Low power, centralized data collection

ABSTRACT

The systems and methods described herein are directed to techniques for improving battery life performance of end devices in resource monitoring systems which transmit data using low-power, wide area network (LPWAN) technologies. Further, the techniques include providing sensor interfaces in the end devices configured to communicate with multiple types of metrology sensors. Additionally, the systems and methods include techniques for reducing the size of a concentrator of a gateway device which receives resource measurement data from end devices. The reduced size of the concentrator results in smaller, more compact gateway devices that consume less energy and reduce heat dissipation experienced in gateway devices. The concentrator may comply with modular interface standards, and include two radios configured for transmitting 1-watt signals. Lastly, the systems and methods include techniques for fully redundant radio architecture within a gateway device, allowing for maximum range and minimizing downtime due to transmission overlap.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation application which claims priority to commonlyassigned, U.S. patent application Ser. No. 15/935,285, filed Mar. 26,2018, which claims priority to U.S. patent application Ser. No.15/423,500, filed Feb. 2, 2017, now U.S. Pat. No. 9,929,771 issued Mar.27, 2018, which claims priority filing benefit from U.S. ProvisionalPatent Application Nos. 62/292,147, filed Feb. 5, 2016, and 62/432,431,filed Dec. 9, 2016. Application Ser. Nos. 15/935,285 and 15/423,500,U.S. Pat. No. 9,929,711, and U.S. Provisional Patent Applications62/292,147 and 62/432,431 are all fully incorporated herein byreference.

BACKGROUND

Resource monitoring systems use various types of sensors to gatherresource measurement data to monitor resource consumption forindustrial, commercial and residential uses. As the techniques formonitoring resource consumption continue to evolve, the use of endcomputing devices to provide additional functionality to unsophisticatedsensors has become more commonplace. For example, rather than requiringmanual, human-based collection of resource measurement data from sensorsplaced in geographically disparate locations to determine resourceconsumption, end computing devices may report resource measurement datato centralized locations using wired and/or wireless communications. Dueto the nature of the types of resources being monitored, these enddevices and associated sensors may be placed in remote or difficult toaccess locations. Consequently, it is advantageous for these endcomputing devices to transmit resource measurement data over longerdistances.

Remote or otherwise inaccessible end devices may be coupled to sensorsin locations where external power supplies are not readily available,thereby requiring the use of internal power supplies, such as batterypower. As the distance end devices transmit resource measurement dataincreases, so does the drain on these internal supplies, which resultsin requiring for more frequent manual replacement of internal powersupplies, which is time and cost intensive. Thus, users of end computingdevices in resource monitoring systems experience a trade-off betweentransmission distance and longevity of internal power supplies.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features.

FIG. 1 illustrates an example environment including an end devicecoupled to one or more sensors collecting resource measurement data, anda gateway device receiving the resource measurement data from the enddevice over one or more networks.

FIG. 2 illustrates an example environment including end device(s),gateway device(s), service provider(s), and computing device(s), forcollecting resource data and monitoring resources.

FIG. 3 illustrates a graphic representation of an end device receivingsensor data from a sensor, and transmitting the sensor data to a gatewaydevice.

FIG. 4A illustrates a graphic representation of components of an exampleend device.

FIG. 4B illustrates a graphic representation of another example enddevice

FIG. 5 illustrates example components of a transceiver of an end device.

FIG. 6 illustrates an example power supply that can be implemented in anend device.

FIG. 7 illustrates an example process for transmitting a signal, by anRF transceiver of a computing device, according to a duty cycle of thecomputing device.

FIG. 8 illustrates an example sensor interface of an end deviceconfigured to communicate with various sensors.

FIG. 9 illustrates an example process for determining a sensor type of asensor associated with an input cable coupled to a first input port, andapplying a voltage to an input port to receive data from the sensorbased on the type of sensor

FIG. 10 illustrates an example process for receiving data and storingdata by a comparator circuit according to a duty cycle.

FIG. 11 depicts an example housing for an end device.

FIG. 12 illustrates a graphic representation of an example concentrator.

FIG. 13 illustrates a component layout of an example concentrator,including light emitting diodes (LEDs) of the example concentrator.

FIG. 14 illustrates example exterior views of a concentrator whichillustrate dimensions of the concentrator.

FIG. 15 illustrates the small form factor of a concentrator relative toa quarter to give reference as to the small size of the concentrator.

FIG. 16 is an example graphical user interface (GUI) that illustrates asuspected event report and/or alert. A service provider may generate theGUI based on data received from an end device or a gateway device.

FIG. 17 is an example GUI that illustrates water usage for a monitoringlocation. A service provider may generate the GUI based on data receivedfrom an end device or a gateway device.

FIG. 18 is another GUI illustrating water usage for a monitoringlocation. A service provider may generate the GUI based on data receivedfrom an end device or a gateway device.

FIGS. 19A-19D are GUIs that illustrate an automated waste event trackingsystem. The GUIs provide an interface for a service provider to generatea report for one or more customers and provide recommendations to theone or more customers.

FIG. 20 is a GUI illustrating an analytics log for detected wasteevents. A service provider may generate the GUI based on data receivedfrom an end device or a gateway device.

FIG. 21 is a GUI illustrating an automated alert tracking page forproviding a user with capabilities to track alerts provided by a serviceprovider.

FIG. 22 is a GUI illustrating an interface for a service provider togenerate and manage alerts for a monitored location.

FIGS. 23A and 23B are GUIs illustrating information and anomaliesregarding resource consumption information for a monitored site.

DETAILED DESCRIPTION

Embodiments of this disclosure are directed to techniques for improvingbattery life performance of end devices in resource monitoring systemswhich transmit data using low-power wide area network (LPWAN)technologies. Further, embodiments described herein include techniquesfor providing end devices configured to interface with multiple types ofsensors, thereby increasing the functionality, versatility, andinterchangeability of the end devices. Additionally, the embodimentsdescribed contemplate techniques for reducing the size of a concentratorof a gateway device of resource monitoring systems which receiveresource measurement data from the end devices. Reducing the size of theconcentrator of gateway devices may result in smaller, more compactgateway devices that consume less energy by reducing heat dissipationexperienced in gateway devices with larger concentrators. Additionally,reducing the size of the concentrator also allows for use in mobileapplications (e.g., mounted on an unmanned aerial vehicle). Further,reducing the concentrator size may allow the concentrator to beimplemented into existing form factors that allow the concentrator to beplugged into open hardware sockets for increased functionality.

Resource monitoring systems may include networks of devices, such as oneor more end devices coupled to sensors to monitor resources atmonitoring locations and to transmit resource measurement data to one ormore gateway devices. In various examples, the end devices may transmitresource measurement data using LPWAN technologies (e.g., LoRaWAN®,GREENWAVE®, etc.) to provide low-power communications over longerdistances than the communications provided using short-range wirelesscommunication technologies (e.g., ZIGBEE®, BLUETOOTH®, etc.).

In some examples, the end devices may be located such that externalpower supplies are unavailable, and may be powered using an internalpower supply (e.g., batteries, battery banks, etc.). Depending on thedistance the end device must transmit the resource measurement data, thesignals carrying the data may be relatively high power signals (e.g.,½-watt, 1-watt, etc.). In various examples, however, peak currentprovided by internal batteries may be insufficient for an end device totransmit high power signals. Techniques described herein contemplate theuse of a supercapacitor to provide sufficient power for these relativelyhigh power communications. In some examples, batteries of the end devicemay provide power to the system components (e.g., microprocessor,voltage converters, etc.), whereas the supercapacitor may provide powerto the transceiver for the relatively high power transmissions. In someexamples, the end device may periodically transmit the resourcemeasurement data. In such examples, the supercapacitor may only supplypower to the transceiver and/or transceiver components while in acommunication mode for small periods of time (e.g., 10 milliseconds, 100milliseconds, etc.), and remain in a low power mode for longer periodsof time (e.g., 30 seconds, 1 minute, 5 minutes, etc.). In some examples,the supercapacitor may at least partially discharge when providing powerto the transceiver in communication mode. Once the supercapacitor hasfinished supplying power to the transceiver to transmit a signal, thebatteries may recharge the supercapacitor during the lower power modefor the longer periods of time to charge the supercapacitor for the nexttransmission. In this way, the end devices may receive and storeresource measurement data from sensors using battery power while in thelower power mode, and transmit the resource consumption dataperiodically using relatively high power signals powered by thesupercapacitor.

In some examples, the end device may include a gas gauge having acoulomb counter. The coulomb counter may count the coulombs (e.g.,ampere-second) leaving the batteries to charge the supercapacitor duringthe low power mode to determine how much energy is leaving the batteriesand/or how much energy remains in the batteries. In some examples, thegas gauge may limit the amount of current leaving the batteries fromgoing above a threshold coulomb count to prevent the batteries fromdischarging too quickly when charging the supercapacitor. In someexamples, this may extend the life of the batteries.

In various examples, the end device may include a sensor interfaceconfigured to interface with multiple types of sensors. For example, thesensor interface may allow the end device to receive data from multipletypes of sensors, including 3-wire Automatic Meter Reading (AMR)sensors, Hall effect sensors, reed switch sensors, Pulses sensors, andmagneto-resistive sensors. In various examples, the sensor interface mayinclude a single connection which is configured to accept inputs fromall the above sensors (e.g., using multiple ports) and collect data fromthe sensors using the single connection. In this way, the end device mayprovide additional functionality, versatility, and completeinterchangeability between a plurality of sensor types.

In some examples, the end device may have a duty cycle by which datacollection circuits or modules are powered on to receive resourcemeasurement data from the sensors, and powered down to conserve batterypower. In some instances, the duty cycle may be fixed or predefined forthe end device upon manufacture and/or installation. In variousexamples, the end device may include one or more modules, circuits,and/or algorithms configured to dynamically modify the duty cycle bywhich the end device receives sensor data through the port of the sensorinterface. As an example, the end device may determine a type of sensorthat is providing data to the end device through the sensor interface.In some examples, the end device may receive an indication of the typeof sensor in various ways. For example, the end device may receive anindication of the sensor type over a network from one or more servercomputing devices, or from another computing device via a cableconnected to another input port of the end device (e.g., UniversalSerial Bus (USB) port, Universal Asynchronous Receiver/Transmitter(UART) port, etc.). In some examples, the end device may cycle throughthe sensor types to determine which type of sensor is providing datathrough the sensor interface, or infer the sensor type based on a formator type of data received from the sensor.

As noted above, the duty cycle by which data collection and storagecircuits or modules of the end device are powered on to receive resourcemeasurement data from the sensors, and powered down to conserve batterypower, may be dynamically modified based on the type of sensor. Forexample, the end device may calculate, or receive over the network fromserver computing devices, an updated duty cycle. The updated duty cyclemay be based on various parameters of the type of sensor, such as arotational speed of the sensor, a rate at which the sensor outputspulses, etc. In various examples, by dynamically changing the dutycycle, the power down time periods of the duty cycle may be extended,which thereby saves battery power, while ensuring that the datacollection and storage components and circuits are powered on at theappropriate times to maintain efficient data collection and storage(e.g., to prevent “dropping” of measurements).

In some examples, a gateway device may include a concentrator which hasa small form factor. For example, the concentrator may have dimensionsof approximately 1.3″×0.96″×0.19″ resulting in a total volume ofapproximately 0.24 in³. In some examples, the small size of theconcentrator may require efficient use of power and result in less heatdissipated from the concentrator due to losses. In some examples, theconcentrator may comply with the XBee® interface standard. Further, theconcentrator may include two radios with antennas to allow forsimultaneous dual channels or diversity operation, with both antennaslistening to the same channel. In some examples, both radios areconfigured to transmit signals at a power of 1-watt simultaneously atdiffering frequencies.

In various embodiments, the techniques and/or systems described hereincan improve a functioning of end devices by reducing an amount ofbattery power consumed by end devices and/or gateway collection devices.Further, despite reduced power consumption and increased battery life,the techniques and/or systems described herein enable high-resolutiontransmission of resource data (e.g., every second, minute, etc.). Thus,the systems and methods improve equipment operation, save battery life,provide high power transmission of signals, and maintain functionalityfor end devices and gateway collection devices, among other benefits.

Example Architectures

FIG. 1 illustrates an example environment 100 including one or moregateway devices 102 to receive resource measurement data from one ormore end devices 104 and 106 for monitoring resources at a monitoringlocation 108, in accordance with embodiments of the disclosure.

In some embodiments, the monitoring location 108 can represent awarehouse, grocery store, restaurant, car wash, office building,residence, oil refinery, agricultural installation (e.g., a farm),shipping location, or any location that uses one or more resources, suchas resource 110. As can be understood in the context of this disclosure,the resource 110 can include one or more resources such as water,electricity, air, fuel (gasoline, diesel, kerosene, etc.), or the like,and in some embodiments, can include inputs and/or outputs to and fromthe monitoring location 108. For example, the resource 110 can representclean or potable water and/or waste water.

The monitoring location 108 can include one or more gateway devices 102and one or more end devices 104 and 106, which are operatively coupledwith one or more sensors, 112, 114, and 116, respectively. Asillustrated in FIG. 1, the sensor 112 provides input to the gatewaydevice 102, the sensor 114 provides input to the end device 104, and thesensor 116 provides input to the end device 106. In some embodiments,each piece of equipment (also referred to as a node) may include asensor to monitor the resources for each individual node. In someembodiments, one or more sensors can be coupled with an individualgateway device or an individual end device. In some embodiments, the enddevices 104 and 106 can wirelessly communicate with the gateway device102, which in turn can wirelessly communicate with network(s) 118. Insome embodiments, the gateway device 102 can communicate directly withthe network(s) 118. In some embodiments, the gateway device 102 and theend devices 104 and 106 can form a mesh network, with the gateway device102 providing a communication interface with the network(s) 118. In someembodiments, the gateway device 102 and the end devices 104 and 106 cancommunicate with the network(s) 118 via channels not provided on anetwork or communication means provided by the monitoring location 108.That is to say, the gateway device 102 and the end devices 104 and 106can communicate with the network(s) 118 independently from themonitoring location 108 to reduce network congestion and to improvenetwork security. In some embodiments, the gateway device 102 and theend devices 104 and 106 can communicate with the network(s) 118 via anywired or wireless connections. The gateway device 102 and the enddevices 104 and 106 are also discussed in connection with the variousfigures of the disclosure, below.

The monitoring location 108 can include, but is not limited to, one ormore pieces of equipment (or nodes) such as cooling tower(s) 120 (e.g.,evaporative cooling processes and/or systems), car wash(es) 122, waterconditioner(s) 124, sink(s) 126, restroom(s) 128, and/or equipment 130and 132, such as heaters, computers, televisions, mobile phones, lights,pumps, buildings, irrigation, electrical, gas, HVAC, programmable logiccontrollers, sensors, etc. As can be understood in the context of thisdisclosure, the monitoring location 108 can represent any type ofbusiness, government, industrial, institutional, school, hospital, landscape, agricultural, and/or residential facility, and can include anyassociated equipment 130 and 132. Further, the monitoring location 108can include additional sensors for monitoring or measuring an occupancyof the monitoring location 108, environmental sensors for monitoring ormeasuring temperature, humidity, pressure, conductivity of resources,chemical composition (e.g., pH) of resources, or weather at themonitoring location 108, and/or a security system at the monitoringlocation.

In some embodiments, the equipment 132 can be located outside of themonitoring location 108, and can be located in a separate building,above ground, or below ground. In some embodiments, the equipment 132can monitor a same or a separate resource as the resource 110. Asdescribed in connection with the various figures of this disclosure, theequipment 132 can be located at a site where hard wired power is notavailable, or where it is not practical or economical to provide power(e.g., in a field, underground, in a well, etc.). In some embodiments,the end device 106 can use battery power and low power transmitters andreceivers to communicate with the gateway device 102. In such a case,this implementation can reduce installation costs at the monitoringlocation 108.

In some embodiments, one or more sensors 112, 114, and 116 can be usedto monitor resources consumed at the monitoring location 108. Forexample, each piece of equipment can be associated with a unique sensor,while in some embodiments, only one sensor can be used, to monitor awater main or electrical main, for example. In some embodiments,multiple types of resources can be monitored at the monitoring location,such as water and electricity consumption. In some embodiments, datafrom multiple sensors can be combined and/or analyzed together togenerate a virtual node with an associated resource consumption. Forexample, telemetry data from the cooling tower(s) 120 provided by thesensor 114 can be used to remove the effect of the cooling tower(s) 120on the resource consumption monitored by the sensor 112. In someembodiments, multiple sensors can be used to increase a resolution ofdata provided by the systems and methods described herein. In someembodiments, data from multiple sensors can be determined and correlatedto provide insight into operations at the monitoring location 108. Forexample, the occupancy of the monitoring location 108 can be determinedalong with water and/or electricity usage to determine operationaland/or mechanical waste and/or to determine when a resource consumptionis within operating procedures. In another example, a conductivity or pHof water in an evaporative cooling system can be monitored inconjunction with water and/or electricity usage to determine operationaland/or mechanical waste and/or to determine when a resource consumptionis within operating procedures. In another example, water temperature ismonitored to verify within limits for proper handwashing (e.g., for foodhandlers, hospitals, etc.). In another example, air temperature ismonitored to ensure freezers and refrigerators within limits for foodsafety and to maximize storage time and minimize waste.

In some embodiments, the resource consumption can be normalized using avariety of factors, such as location size, location capacity, locationproductivity, number of persons, number of objects produced, etc. Forexample, these normalization factors can be monitored by the gatewaydevice 102, the end device(s) 104 and 106, or additional equipment atthe monitoring location 108, and/or the normalization factors can beobtained from a third-party. For example, to monitor customer traffic ata location, the monitoring location 108 and/or the gateway device 102can include a video camera counting a number of unique faces at themonitoring location 108, thereby providing an accurate count of thenumber of individuals (or number of individuals per minute, hour, etc.)at the monitoring location. By way of another example, weatherinformation can be obtained from public or private weather sources, suchas the Internet.

FIG. 2 illustrates an example environment 200 including one or moregateway devices 202, one or more end devices 204, one or more serviceproviders 206, and one or more computing devices 208, for collectingresource data and monitoring resources.

The example environment 200 is usable to implement the techniques andsystems described herein. The environment 200 includes a plurality ofdevices such as gateway device(s) 202 and end device(s) 204 configuredto gather and process data described herein. The environment 200 alsoincludes one or more service provider(s) 206 that can further provideprocessing and analytics. The service provider(s) 206 is configured tocommunicate alerts, reports, analytics, graphical user interfaces, etc.,to the computing device(s) 208 and/or the gateway device 202, forexample. In various examples, the gateway device(s) 202, the enddevice(s) 204, the service provider(s) 206, and the computing device(s)208 can communicate via one or more networks 210.

The gateway device(s) 202 can individually include, but are not limitedto, any one of a variety of devices, including portable devices orstationary devices. For instance, a device can comprise a data logger,an embedded system, a monitoring device, a smart phone, a mobile phone,a personal digital assistant (PDA), a laptop computer, a desktopcomputer, a tablet computer, a portable computer, a server computer, orany other electronic device.

The gateway device(s) 202 can include one or more processor(s) 212 andmemory 214. The processor(s) 212 can be a single processing unit or anumber of units, each of which could include multiple differentprocessing units. The processor(s) 212 can include a microprocessor, amicrocomputer, a microcontroller, a digital signal processor, a centralprocessing unit (CPU), a graphics processing unit (GPU), a securityprocessor etc. Alternatively, or in addition, some or all of thetechniques described herein can be performed, at least in part, by oneor more hardware logic components. For example, and without limitation,illustrative types of hardware logic components that can be used includea Field-Programmable Gate Array (FPGA), an Application-SpecificIntegrated Circuit (ASIC), an Application-Specific Standard Products(ASSP), a state machine, a Complex Programmable Logic Device (CPLD),other logic circuitry, a system on chip (SoC), and/or any other devicesthat perform operations based on instructions. Among other capabilities,the processor(s) 212 can be configured to fetch and executecomputer-readable instructions stored in the memory.

The memory 214 can include one or a combination of computer-readablemedia. As used herein, “computer-readable media” includes computerstorage media and communication media.

Computer storage media includes volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer-readable instructions, data structures,program modules, or other data. Computer storage media includes, but isnot limited to, phase change memory (PRAM), static random-access memory(SRAM), dynamic random-access memory (DRAM), other types of randomaccess memory (RAM), read only memory (ROM), electrically erasableprogrammable ROM (EEPROM), flash memory or other memory technology,compact disk ROM (CD-ROM), digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium that canbe used to store information for access by a computing device.

In contrast, communication media includes computer-readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave. As defined herein,computer storage media does not include communication media.

The memory 214 can include an operating system configured to managehardware and services within and coupled to a device for the benefit ofother modules, components and devices. In some embodiments, the one ormore gateway device(s) 202 can include one or more servers or othercomputing devices that operate within a network service (e.g., a cloudservice), or can form a mesh network, etc. The network(s) 210 caninclude the Internet, a Mobile Telephone Network (MTN), Wi-Fi, cellularnetworks, mesh networks, and/or other various communicationtechnologies.

The techniques discussed above can be implemented in hardware, software,or a combination thereof. In the context of software, operationsrepresent computer-executable instructions stored on one or morecomputer-readable storage media that, when executed by one or moreprocessors, configure a device to perform the recited operations.Generally, computer-executable instructions include routines, programs,objects, components, data structures, and the like that performparticular functions or implement particular abstract data types.

The gateway device(s) 202 can, at its simplest, include no sensors.Alternatively, the gateway devices(s) 202 can include one or moresensors 216, including but not limited to, a water meter, an electricalmeter, a gas meter, a heating, ventilation, and air conditioning (HVAC)sensor/monitor, and/or any generic or specialized sensor input. Thesensors 216 can continuously or periodically monitor data at anyinterval, or upon request. In some embodiments, the gateway device(s)202 can include one or more expansion ports to receive additionalsensors or to receive additional sensor data. In some embodiments, thesensors 216 receive one or more pulses or data from a sensor integratedwith a plant utility, such as a water sensor in-line with a water mainin a building. In some embodiments, one or more inputs and/or sensors216 can be optically isolated to protect the gateway device(s) 202 fromdamaging inputs.

The gateway device(s) 202 can also include a power module 218 thatreceives power from a network such as a power grid, and can also includeone or more uninterruptable power supplies (UPS) to power the gatewaydevice(s) 202 when the power grid is interrupted. For example, the powermodule 218 can include a timer that determines a condition when powerhas been absent for too long and can shut down the gateway device(s) 202without crashing, damaging, or losing data of the gateway device(s) 202.In some embodiments, the power module includes one or more powerfilters. In some embodiments, the power module 218 can monitor a powersupply while the gateway device(s) 202 is in a powered-down state andcan restart the device when power is restored. In some embodiments, thepower module 218 can send an error message when a power outage isdetected. In some embodiments, the power module 218 can provide enoughpower after power loss to allow for continued transmission of sensor 216data and/or continued communications with end device 204 or overnetwork(s) 210.

The gateway devices(s) 202 can include a communication module 220 tocommunicate with other gateway devices or end devices (e.g., in meshnetwork) and/or to communicate via the network(s) 210. For example, thecommunication module 220 can include antennas to communicate with theend device(s) 204 via any low power, long range wide area network. Insome embodiments, the communication module 220 can negotiate with theend device 204 to determine an optimal radio link to maximize thebattery life of the end device 204, for example. These and furtheraspects of the communication module 220 are described in connection withthe various figures of this disclosure. In some examples, the gatewaydevice(s) 202 may further include a concentrator 262 including twoindependent radio frequency paths, each with transmit and receivecapability. In some examples, the concentrator 262 may comply withvarious standards, such as the XBee® interface standard and allows forcohabitation with other radios, including ISM, cellular, and Wi-Fi.Further discussion of details of the concentrator 262 can be found inthe description of FIGS. 12-15.

In some embodiments, the gateway device(s) 202 can include one or moredisplays, LEDs, buzzers, and/or speakers to provide visual or audiointerfaces (e.g., with text-to-speech capabilities) to present thealerts and/or reports discussed herein to a user located at the gatewaydevice 202. For example, the user can interact with the gateway device202 to review the alerts, reports, recommendations, etc., and implementmeasures to reduce waste at the site. After addressing or resolving anissue, the user can interact with the gateway device 202, eitherdirectly (e.g., via a touchpad display, on-board buttons, keyboard,microphone, etc.) or through the cloud (e.g., smart phone app, webserver, etc.) to indicate a state of the issue, for example, whether theissue was resolved, whether the recommendation was helpful, whether theissue was not resolved, etc. In some embodiments, after receiving theindication at the gateway device 202, the indication can be transmittedto the service provider 206 for review and incorporation into theanalytics, reports, recommendations, etc.

The end device(s) 204 can include one or more processor(s) 222, a memory224, sensors 226, a power module 228, and a communication module 230,each of which can be implemented similar to the processor(s) 212, thememory 214, the sensors 216, the power module 218, and/or thecommunication module 220 of the gateway device(s) 202. In someembodiments, the end device 204 can operate remotely from gateway device202, for example, at the bottom of a well. In such an example, the enddevice 204 can monitor a pump, or the like. In some embodiments, thesensor 226 can include a 3-wire Automatic Meter Reading (AMR) unit(coupled with a sensor or protocol provided by SENSUS, NEPTUNE, and/orK-FRAME, for example), an interface with a Hall effect/magnetoresistivesensor, an inductive-capacitive (LC) sensor, and/or a pulse sensorinterface. In some embodiments, the power module 228 can include alithium battery, such as a lithium-thionyl chloride (Li—SOCl₂) battery.In some embodiments, the communication module 230 can communicate withthe gateway device 202 via one or more antennas, communicating at withinone or more industrial, scientific, and medical (ISM) bands, such as 915MHz in the United States, 868 MHz/433 MHz in Europe, 430 MHz inAustralia, 923 MHz in Japan, etc., for example, in accordance with theparticular protocol and/or particular implementation location. In someembodiments, the communication module 230 can be configured inaccordance with various operating region requirements. In someembodiments, the end device 204 can transmit and receive data via a longrange, wide area network, for example, in accordance with a LoRamodulation protocol provided by SEMTECH, or in accordance with theLoRaWAN specification provided by the LoRa Alliance. In someembodiments, the communication module 230 includes a GFSK (GaussianFrequency Shift Keying) or FSK (Frequency Shift Keying) link capability.In some embodiments, the communication module 230 can communicate viaany one of IEEE 802.11, Wi-Fi, cellular, 3G or 4G LTE networks, LAN,WAN, wired or wireless networks, etc. Further details of the end device204 and the gateway device 202 are provided in connection with FIGS.3-15.

The service provider(s) 206 can include one or more processor(s) 232, amemory 234, and a communication module 236, each of which can beimplemented similar to the processor(s) 212, the memory 214, and/or thecommunication module 220 of the gateway device(s) 202.

In some embodiments, the service provider(s) 206 can include ananalytics module 238, including one or modules such as a historical data240 module, a resource signatures 242 module, a report/alert module 244,an automated analysis 246 module, a graphical user interfaces 248module, and/or a device management module 250.

In some embodiments, the analytics module 238 can receive inputregarding resource usage from the gateway device(s) 202 and/or the enddevice 204 and can analyze the data to generate historical data.Further, the analytics module 238 can receive data and compare the datawith historical data to determine a suspected event. In someembodiments, the analytics module 238 can compare current and/orhistorical data between a plurality of locations. In some embodiments,the analytics module 238 can normalize the current and/or historicaldata by factors such as site usage, site production, temperature,weather, etc., using data gathered from sensors at the monitoringlocation and/or gathered from third party sources. In some embodiments,the analytics module 238 can determine mechanical and/or operationalwaste. In some embodiments, the analytics module 238 can generate one ormore signatures indicating a resource usage, such as a correct orincorrect resource usage. In some embodiments, the analytics module 238can generate one or more reports, alerts, recommendations, and/orgraphical user interfaces.

In some embodiments, the service provider performs analytics to map realtime and historic resource usage, as well as specific identifiedevents: 1) to a specific alert's subject, text, images, manuals,receiver list, threshold categorization, etc.; and/or 2) for inclusionin historic reports for management, administrators, executives,sustainability reports, compliance reporting, motivational programs,gamification features, etc.

In some embodiments, resource consumption data is combined with metadata(e.g., site specific or node specific operations knowledge, etc.) tocreate transparency on managerial and operational practices such ascompliance with Best Management Practices, Standard OperatingProcedures, and managerial success at controlling waste, optimizingresource usage, etc. This same data can also be compared across multiplelocations for the purpose of managerial reporting, sustainabilityprogram compliance reporting, equipment calibration, actual versespredicted consumption reports, vendor accountability, value engineering,resource dependency relative to sector, compliance reporting, and forstaff motivational initiatives such as competitions between sites,gamification of efficient resource use at a given site, between sites,companies, sectors, etc.

For example, in a carwash operation, the high resolution reporting andanalytics can automatically compare water use at different parts of thecarwash train for a standard vehicle across many locations, the specificsite's past tests, manufacturer claims, similar car wash units, industrystandards, etc.

In this example, anomalies in the carwash resource usage informationtrigger event specific responses that are formed by mapping specificsubparts of the alert to text, graphics, manuals, customer specific ornode specific best management practices and or standard operatingprocedures. Exemplary alerts, text, graphic, and reports that can beadapted for detailing usage information and specific events aredescribed in connection with FIGS. 16-23B of this disclosure.

In some embodiments, the events and reports are tracked in real time andthe data can be used to drive staff motivational initiatives to rewardlocations for quick resolution of waste events in a recognition mode orgamification mode where points are accrued and reported in a way thatallows sites and individuals to compare and compete for optimal resourceusage in a gaming and or managerial recognition platform. Metrics suchas fewest gallons of water, kwh of electricity, etc. per car washed gainpoints in the gaming environment as do other corporate andsustainability inputs to create an interactive environment where staffand stakeholders are motivated by gaming and recognition techniques tooptimize resource consumption, corporate and sustainability initiatives.

In another example relating to a cooling tower and/or evaporativecooling systems, the high resolution reporting and analytics canautomatically compare water use at different loading temperatures, atdifferent water conditions (e.g., conductivity, pH, temperature,pressure, flow rates, etc.), weather conditions, previous operatingconditions at the site, other cooling towers of similar capacityoperating under similar or varying loading and weather conditions, aswell as other metadata to identify specific waste events andopportunities for resource use optimization.

In this cooling tower example, anomalies in the above informationtrigger event specific responses that are formed by mapping specificsubparts of the alert to text, graphics, manuals, customer specific ornode specific best management practices and or standard operatingprocedures. Exemplary alerts, text, graphic, and reports that can beadapted for detailing usage information and specific events aredescribed in connection with FIGS. 16-23B of this disclosure.

The real time and historic data can be used to drive staff motivationalinitiatives to reward locations for quick resolution of waste events (oroptimization innovations submitted) in a recognition mode orgamification mode where points are accrued and reported in a way thatallows sites and individuals to compare and compete for optimal resourceusage in a gaming and or managerial recognition environment.

In some embodiments, the device management module 250 can monitor thestatus of the gateway device(s) 202 and/or the end device(s) 204 todetermine if the devices are operating within nominal ranges. In theevent the devices 202 and/or 204 are indicating a problem (or inresponse to other feedback from the devices 202 and/or 204), the devicemanagement module 250 can generate an alert to investigate the devices.In some embodiments, the device management module 250 can monitor andchange the communication and reporting characteristics of the gatewaydevice(s) 202 and end device(s) 204 to minimize power usage. Forexample, the device management module 250 can control a resolution ofdata (e.g., data recorded every second, every minute, hourly, weekly,monthly, etc.). In some embodiments, the device management module 250can set whether devices 202 and 204 are push devices (e.g., the devicesinitiate communication on their own when data is to be transmitted) orpull devices (e.g., the devices wait for data to be requested by thegateway device(s) 202 or the service provider(s) 206). In someembodiments, the device management module 250 can control transmissionpower of the device 202 and/or 204.

The computing device(s) 208 can include one or more processor(s) 252, amemory 254, and a communication module 256, each of which can beimplemented similar to the processor(s) 212, the memory 214, and/or thecommunication module 220 of the gateway device(s) 202. Further, thecomputing device(s) 208 can include graphical user interfaces 258 todisplay or otherwise present graphical user interfaces at the computingdevice(s) 208, as described in connection with FIGS. 16-23B.

The environment 200 also includes one or more users 260 to employ thecomputing device(s) 208. The one or more users 260 can interact with thecomputing device(s) 208 to perform a variety of operations.

FIG. 3 illustrates a graphic representation of a system 300 including asensor 302, an end device 304, and a gateway device 306, for example.The components in FIG. 3 (and throughout the disclosure) are for examplepurposes only, and the systems, devices, and techniques described hereinare not limited to the specific examples, implementations, components,and/or architectures discussed or illustrated herein.

In some embodiments, the end device 304 performs the function ofcapturing data from its connected sensors, such as the sensor 302. Forexample, an end device 304 can be connected to a water flow meter andcan capture and/or read water flow volume (e.g., total flow,instantaneous flow, flow over a period of time, etc.) passed through thewater sensor. This data can be timestamped (e.g., at the end device 304)and can be transmitted (e.g., reported) to the gateway device 306.Exemplary sensor data in the context of water may include but is notlimited to, temperature, humidity, pressure, flow rate, conductivity,pH, optical clarity, turbidity, etc. In some embodiments, the end device304 may be connected to one or more sensors 302 via one or more wired orwireless connections. For example, the connections may include, but arenot limited to, one or more of Modbus protocol, M-Bus protocol, WirelessM-Bus protocol, L-Bus protocol, RTH protocol, HART protocol,WirelessHART protocol, ZigBee, Sensus UI-1203 protocol, Neptune ARB Vprotocol, Neptune ProRead protocol, legacy 2-wire TouchRead protocol,K-Frame protocol, etc., and any protocols or standards discussed herein.In some embodiments, the end device 304 may pull data from the sensor302, and in some embodiments, the sensor 302 may push data to the enddevice 304. For example, the end device 304 query a sensor 302 to readone or more registers associated with the sensor 302, or the end device304 may receive data transmitted by the sensor 302 to the end device304.

In some embodiments, the end device 304 may function as a repeater foradditional end devices. That is, in some instances, an end device maytransmit data to the end device 304, which may subsequently transmit thedata to the gateway device 306. In some embodiments, the end device 304may function as a converter for additional end devices or sensors thatcommunicate using company-specific or otherwise proprietary protocolsmay transmit data to the end device 304, which may subsequently convertnonstandard or proprietary data into a standard or non-proprietaryprotocol, which may subsequently transmit the data to the gateway device306.

In some embodiments, communication between the end device 304 and thegateway device 306 can be a radio link using a modulation techniqueand/or transceiver in compliance with a SEMTECH LoRa modulationtechnique and/or transceivers. In some embodiments, communicationbetween the gateway device 306 and one or more end devices 304 may befacilitated by a SEMTECH transceiver using LoRa modulation techniques,or by a SEMTECH transceiver using other modulation techniques. Ingeneral, the communication between the gateway device 306 and the one ormore end devices 304 may include any low-power, long-range, wide areanetwork communication protocol.

In some embodiments, the gateway device 306 can include a dataconcentrator between one or many end devices 304. One of the functionsof the gateway device 306 can be to collect data from each end device,format the data, and transmit the data to one or more service providers.For example, the gateway device 306 can push the data to a serviceprovider (such as the service provider 206), or the data can be pulledfrom the gateway device 306.

In some embodiments, communications between the gateway device 306 andthe service provider 206 can be a cellular connection and can use a 4GLTE CAT 1, CAT 3, or CAT-M1 modem. In some embodiments, communicationsbetween the gateway device 306 and the service provider 206 can be aWi-Fi or other wireless LAN (IEEE 802.11), wired LAN (IEEE 802.3),satellite phone (IRIDIUM), wireless personal area network (WPAN) (IEEE802.15). Of course, any wired or wireless connection may be used toprovide communications between the gateway device 306 and the serviceprovider 206.

In some embodiments, the system 300 may operate in accordance with oneor more International Telecommunications Union (ITU) Regions. In someembodiments, the system 300 is operable in ITU Region 1 (e.g., EU868 MHzISM Band (863 to 870 MHz), including Europe, Africa, the Middle East,and the former USSR); in some embodiments, the system 300 is operable inITU Region 2 (US915 MHz ISM Band (902 to 928 MHz), including North andSouth America); and in some embodiments, the system 300 is operable inITU Region 3 (China 779 to 787 MHz ISM Band, which allows for operationin most of Asia, Indonesia, India, and Australia; AS923 915-928 MHz ISMBand, which allows for operation in Japan, Hong Kong, Taiwan, Singapore,Thailand, and others). To adapt the system 300 disclosed herein todifferent regions internationally (ITU Region 1, 2, or 3), someembodiments include changing of the RF (radio frequency) components(e.g., surface acoustic wave (SAW) filter, lumped element matching,antenna, etc.) and software reconfiguration. Generally speaking, thesystem 300 can be adopted to any frequency between 400 MHz to 960 MHz,and can be configured for either LoRa (long range wide area network,such as in accordance with the LoRa Alliance), FSK (frequency shiftkeying), GFSK (Gaussian frequency shift keying), OOK (on-off keying)modulation, or any low power wide area network modulation techniques.

In some embodiments, the antenna(s) coupled to the end device 304 inFIG. 3 may be one or more 915 MHz ISM antennas that can include a GFSKlink capability and/or a 915 MHz ISM link 308. In some embodiments, theend device 304 can include one or more LoRa transceivers includingsoftware that is re-configurable for GFSK modes, allowing for compliancewith IEEE 802.15.4g (WPAN) and Wireless Meter-Bus (M-Bus) protocol(“WMBus”). In connection with the communication link 308, the LoRa PHY(physical) link RF transmit power, bandwidth (BW), and spreading factor(SF) can be dynamically controlled in software on the end device 304. Insome embodiments, the dynamic control can be based uponreceived-signal-strength indicator (RSSI), signal-to-noise ratio (SNR),packet error rate (PER), or channel activity detection (CAD) to minimizepower consumption and maximize range capability without the need tochange hardware configuration. In some instances, a communicationprotocol can be negotiated between the end device 304 and the gatewaydevice 306 based on a number of end devices communicating with thegateway device 306, amount of data to be transmitted, frequency ofcommunication, requested data format, etc. For example, communicationsprotocols may include, but are not limited to, one or more of: astandard compliant with a SEMTECH transceiver; a LoRaWAN® standard; aZigBee standard; a Bluetooth or Bluetooth Low Energy standard; ahaystack standard; an LTE Advanced for Machine Type Communicationsstandard; a MySensors standard; a NarrowBand Internet-of-things (IoT)standard; a NB-Fi standard; an NWave standard; a Random Phase MultipleAccess (RPMA) standard; a Senet standard; a Sigfox standard; a SymphonyLink standard; a ThingPark Wireless standard; an Ultra Narrow Band (UNB)standard; and a Weightless standard.

In some embodiments, the end device 304 can include flowmeter interfaces(e.g., to interface with the sensor 302). In some embodiments, theflowmeter interfaces include software algorithms and/or hardware controlcircuitry to dynamically enable and/or disable the external sensors(such as the sensor 302) and flowmeter interfaces to minimize powerconsumption. In some instances, the flowmeter interfaces may include anywired or wireless protocols. Further, in some instances, the end device304 may communicate with other end devices, for example, to form a meshnetwork, a star network, and/or to extend range of communications whenan end device 304 is out of range of the gateway device 306.

The gateway device 306 can include one or more antennas, as illustratedin FIG. 3. For example, the gateway device 306 can include one or more915 MHz ISM antennas, one or more GNSS (Global Navigation SatelliteSystem) Antennas, and one or more cell antennas, such as Cell Antenna #1and Cell Antenna #2. Although the GNSS Antenna is illustrated as a RHCP(right hand circular polarized) antenna, it may be understood in thecontext of this disclosure that a linearly polarized antenna can be usedas well.

In some embodiments, the GNSS Antenna can receive communications fromone or more global navigation satellite systems (GNSS), including GPS(Global Positioning System), GLONASS (Global Navigation SatelliteSystem), Galileo, and/or BeiDou. In order to improve accuracy, in someembodiments, the gateway device 306 can receive communications from aSBAS (satellite-based augmentation system) such as WAAS (wide areaaugmentation system), EGNOS (European Geostationary Navigation OverlaySystem), and/or MSAS (MTSAT Satellite Augmentation System). In thismanner, the gateway device 306 can be provided with precise positioninformation. Further, this can allow for “open loop installation,”whereby an end-customer can install the gateway 306 anywhere withoutneeding to inform a service provider (such as the service provider 206)of the particular location.

In some embodiments, the gateway device 306 can support A-GPS(assisted-GPS) or A-GNSS (assisted-GNSS). For example, this can includeterrestrial (cellular) tower augmentation of a satellite signal, usingthe assisted-GPS (A-GPS) system, which can significantly increaseweak-signal performance. In some embodiments, this implementation can beideal for building penetration, and can decrease start lock time (e.g.,ephemeris, almanac data, and/or position information downloaded fromcell tower (e.g., from the network 210)), and can provide a roughposition estimate even in the event of satellite failure.

In some embodiments, the gateway device 306 can support SBAS(satellite-based augmentation system). For example, SBAS can providecorrection data to the gateway device 306, which may allow forstationary position accuracy of 2.5 meters (99% circular errorprobability (CEP)).

In some embodiments, using A-GPS, A-GNSS, and/or SBAS can provideprecise time information and location information to the gateway device306. In some embodiments, this can allow for data packet timestampsaccurate to less than 100 ns (nanoseconds), using the GPS PPS (pulse persecond) signal, which can allow for system-wide coordination withreliable time precision. Further, in some embodiments, the trilaterationof end points (such as the end device 304) can be possible with two ormore GPS-enabled gateway devices (such as the gateway device 306)installed within the end device range. For example, using two or moreGNSS- or GPS-enable gateway devices allows the gateway device 306 toapproximate a position of the end device 304.

In some embodiments, the gateway device 306 can receive power and/orcommunications via PoE (Power over Ethernet) and/or PoE+. In someembodiments, the PoE/PoE+ power injector can be internal or external tothe gateway device 306. In some embodiments, the gateway device 306 canreceive power via an external AD-DC converter (a “wall wort”), using aDC barrel power jack connector. Further, as understood in the context ofthis disclosure, the gateway device 306 can receive power via anystandard, non-standard, and/or proprietary connections using differentvoltages and/or power capabilities.

In some embodiments, the Cell Antenna #1 and Cell Antenna #2 of thegateway device 306 can provide antenna diversity to maximize buildingpenetration. For example, the antennas may be placed at angles of up to90 degrees from each other, to maximize reception in randomly-polarizedenvironments, such as buildings. For example, the antennae can be spacedat least twice as far as the transmission wavelength. For example,increasing antennae spacing can introduce antenna receive diversity,providing installation flexibility that allows for modification ofantenna location and antenna-to-antenna spacing/relative orientation,which maximizes the benefit(s) of diversity. At sites with sufficientsignal strength, the antenna may be closer than twice of a distance of atransmission wavelength. As may be understood in the context of thisdisclosure, the transmission wavelength can vary according toimplementation. Non-limiting examples of transmission frequency (whichis proportional to wavelength) are LTE FDD Bands 4 and 13. In someembodiments, the antenna spacing is on the order of 2 feet.

In some embodiments, the Cell Antenna #1 and the Cell Antenna #2 coupledwith the gateway device 306 can provide a cellular connection totransmit meter readings to a service provider, provide communicationsfor A-GPS or A-GNSS, and/or can provide software and/or firmware updatesto the gateway device 306 and/or the end device 304. For example,software and/or firmware updates may determine sampling frequencies,reporting frequencies, sleep periods, etc. of the device to optimizedata resolution and/or device resources, such as battery power. Further,software and/or firmware updates can be implemented for security updatesor updated encryption algorithms, for example.

Example End Device and Methods

FIG. 4A shows a device 400 illustrating the details of an end device,such as the end device 304 of FIG. 3, for example. In some embodiments,the end device 400 includes a microcontroller 402 controlling theoperations of the end device 400. For example, the microcontroller 402can include hardware, software, or firmware to perform or support thefollowing functions, including but not limited to: a Real-Time Clock(RTC); 16-bit timer sensor/flowmeter timing; dynamic control of RFtransceiver; ADC12 for battery voltage; watchdog timer (WDTG); supplyvoltage supervisor (SVS); internal flash used for non-volatile memory;extended scan IF (ESIF) allowing for ultralow power magnetic sensorinterface; port interrupts (PxIV) used for edge-triggering of externalsensors on port 3 (P3IV), edge-triggering of power supplies on Port 1(P1IV), external power detect on Port 3 (P3IV), and for interruptrequest (IRQ) signals from transceiver on port 4 (P4IV); and/or ahumidity and temperature sensor.

In some embodiments, communication between the gateway device (e.g.,gateway device 306) and end devices (e.g., end device 304, 400) can befacilitated over a network such as a radio mesh network in compliancewith LoRa modulation techniques, or other modulation techniques. In someembodiments, the end device 400 can include a transceiver 404, such as aSEMTECH transceiver. In some embodiments, the transceiver 404 can havethe following capabilities: up to −136 dBm sensitivity; 70 dB CWinterferer rejection at 1 MHz offset; able to operate with negative SNR(signal-to-noise ratio), CCR (co-channel rejection) up to 19.5 dB;emulate 49x LoRa demodulators and 1x (G)FSK demodulator; dual digital TX(transmit) and RX (receive) radio front-end interfaces; programmabledemodulation paths; dynamic data-rate (DDR) adaptation; and antennadiversity or simultaneous dual-band operation.

In some embodiments, the transceiver 404 includes a RF amplifier thatcan increase a transmission power to 1 W, which can be enabled and/ordisabled by the microcontroller 402. In some embodiments, thetransceiver 404 can include a SAW (surface acoustic wave) band passfilter that can limit a bandwidth of the receiver, which in someembodiments can improve thermal (kTB) noise and can prevent out-of-bandinterference at the transceiver 404.

In some embodiments, the end device 400 includes a coulomb counterand/or battery voltage regulator 406 for regulating input power from abattery. In some embodiments, the battery is a lithium battery, such asa Li—SOCl₂ battery. In some embodiments, the battery can be coupled witha supercapacitor to provide a constant output voltage and/or to providepower during transient current spikes, which extends the life of thebattery. In some embodiments, the regulator 406 includes an I²Cinterface to function as a coulomb counter and/or to provide currentcontrol. In some embodiments, the regulator 406 can track the totalcoulomb drawn from the battery throughout the operation of the enddevice 400. In some embodiments, this information can be transmitted tothe gateway device 306 to use in monitoring a health of the end device400, such as the state of the battery. In some embodiments, the gatewaydevice 306 can determine an expected lifetime of the battery of the enddevice 400 and/or can adjust an operation of the end device 400 tooptimize an operating lifetime of the end device 400.

In some embodiments, the end device 400 includes an indicator, such as aLED (light emitting diode) to generate an intermittent signal toindicate the device is functioning properly. In some embodiments, theLED can be activated periodically (e.g., every 10 seconds), while insome embodiments, the LED can be activated by a user to check the statusof the end device 400. In some embodiments, the indicator can include alow-power LCD (liquid crystal display) and/or a buzzer, beeper, orspeaker to provide audio feedback.

In some embodiments, the end device 400 can include a counter/totalizerto receive inputs from one or more sensors and/or flowmeters via theinterface 408. For example, the microcontroller 402 can count meteroutput pulses from a pulse-output style meter. In some embodiments,pulse-output style meters can include a reed switch (e.g., for drycontact) and/or an open collector (e.g., for wet contact).

In some embodiments, the sensor interfaces 408 can be coupled to aninterrupt at the microcontroller 402 which can increment the totalizer.In some embodiments, the totalizers can be implemented as hardware,software, or firmware in the microcontroller 402. In some embodiments,the totalizer can be resettable from the gateway device 306. In someembodiments, a time of the last observed pulse (or all observed pulses)can be kept in memory at the microcontroller 402, and can be transmittedto the gateway device 306 with the meter count. In some embodiments, theinterface 408 includes edge-triggered port interrupts.

In some embodiments, the microcontroller 402 includes an ASCII readerconfigured in accordance with a SENSUS protocol. In some embodiments,this can provide another implementation for a sensor to communicate withthe end device 400. In some embodiments, communications can occur via a3-wire interface in accordance with the SENSUS protocol. In someembodiments, sensor data is read from the SENSUS register (ASCIIcharacters) via the interface 408. The time of each last read can bekept in memory and communicated back to the gateway device 306 with themeter count.

In some embodiments, the microcontroller 402 includes a send datafunction that can automatically send data at intervals, where the datainterval time can be programmable by the gateway device 306 or theservice provider 206. In one example, a reporting interval can be on theorder of every second, one or more minutes, hourly, daily, weekly,monthly, etc. In some embodiments, the end device 400 can transmitinformation when queried by the gateway device 306. Thus, the end device400 can operate both in a push mode or a pull mode to transmit data tothe gateway device 306.

In some embodiments, the microcontroller 402 can include dynamic controlof the RF transceiver, such as the transceiver 404. In some embodiments,this allows the microcontroller 402 to optimize the radio link functionto determine the operating configuration of the transceiver 404 byanalyzing the link between the end device 400 and the gateway device306. In some embodiments, optimization will balance radio operation withbattery life. For example, at least two general modes of radio linkoptimization can be selectable. In some embodiments, these radio linkmodes can be selected by the gateway device 306 and/or by the serviceprovider 206, for example.

By way of example, a first mode may be provided to conserve the batteryof the end device 400. For example, the LoRa PHY link RF transmit power,bandwidth (BW), and spreading factor (SF) can be dynamically controlledin software to minimize power consumption and maximize range capabilitywithout the need to change hardware configuration. In some embodiments,this dynamic control can be based on a received-signal-strengthindicator (RSSI), signal-to-noise ratio (SNR), packet error rate (PER),and/or channel activity detection (CAD). For example, the gateway device306 can indicate to the end device 400 the lowest power required toprovide a signal to the gateway device 306.

In some embodiments, a second mode can be provided that configures theradio in the end device 400 for the strongest radio link at the expenseof using more battery power.

In some embodiments, additional modes can be provided utilizing variousmodulation techniques for optimized data transmission and/or powerconservation. For example, the end device 400 and/or the gateway device306 may select a communication protocol based on a number of devices,available wireless resources, signal strength, commonality of softwareand/or hardware, etc.

In some embodiments, the gateway device 306 can monitor the health ofthe end device. By monitoring specific parameters of the end device 400(such as battery power, internal supply voltages, memory status, memoryutilization, temperature, humidity, reporting frequency, data samplingrate, signal strength, location, etc.) the health of end device 400 canbe monitored and reported back to the gateway device 306, and then on tothe service provider 206, for example. In some embodiments, end device400 health can be reported back to the gateway device 306 only whenthere is a change in one or more parameters (or a change is above orbelow a threshold) in order to minimize data transfer, which in turn canextend battery life.

In some embodiments, the end device 400 can include a real-time clock(RTC) in order to time stamp sensor data and to initiate time-drivenevents such as sleep periods, transmit events, and to coordinate receiveslots. In some embodiments, the real-time clock can be implemented inhardware, software, and/or firmware to keep track of time.

In some embodiments, the end device 400 can include a voltage divider, abuck converter, and/or a boost converter to provide various voltagelevels to the components of the end device 400.

In some embodiments, when implementing a 3-wire automatic meter reading,in accordance with the SENSUS protocol, the sensor interface 408 caninclude a shared power and clock line. In some embodiments, the clockline and power lines can be provided separately.

In some embodiments, the interface 408 and/or a USB bridge can beprovided for diagnostics and/or firmware or software updated to the enddevice 400. In some embodiments, the interface 408 and/or a USB bridgecan be the primary method for transferring sensor data from and controldata to the end device 400.

FIG. 4B illustrates a graphic representation of components of an exampleend device 410, such as end device(s) 104, 106, 204, and/or 304. In someexamples, the components of the end device 410 may be placed on one ormore printed circuit boards (PCBs), disposed on an interior of a housingof the end device 410, or disposed exterior to the housing of the enddevice 410.

In some examples, the end device 410 includes a microcontroller 412 forcontrolling the operations of the end device 410. The microcontroller412 may include various hardware, software, or firmware to perform orsupport the functions of the end device 410, including but not limitedto: a 16-bit RISC processor with a 32-bit Hardware Multiplier operatingat an 8 MHz frequency; 128 kilobytes (KB) of ferroelectric RAM (FRAM); 2KB of SRAM; a general-purpose input/output (GPIO) pin; anencryption/decryption coprocessor (e.g., crypto-accelerator) for variousencryption standards, including 128- and 256-AES (Advanced EncryptionStandard); timers including five 16-bit timers and 14 totalcapture/compare timers; one USB communication through an external port;1 serial peripheral interface (SPI) bus; an I²C serial computer bus; aReal-Time Clock (RTC); and/or a Real-Time Clock reference at 32.768 kHzXTAL.

In some embodiments, communication between the gateway device (e.g.,gateway device 306) and end devices (e.g., end device 304, 410) can befacilitated over a network such as a radio mesh or star network incompliance with LoRa modulation techniques, or other low power wide areanetwork modulation techniques. In some embodiments, the end device 410can include an RF transceiver 414, such as a SEMTECH transceiver. Insome embodiments, the RF transceiver 414 can have the followingcapabilities: up to −137 dBm sensitivity; software-configurable LoRamodulator/demodulator and (G)FSK modulator/demodulator; dual TX(transmit) and RX (receive) radio front-end interfaces; programmabledemodulation paths; dynamic data-rate (DDR) adaptation; and antennadiversity or simultaneous dual-band operation.

In some examples, the RF transceiver 414 may communicate with devices,such as gateway device(s) 102, 202, and/or 306. In some embodiments, thetransceiver 414 may have various communication paths, such as a firsttransmit (TX) path 416, a second transmit path 418, and a receive (RX)path 420. In some examples, the RF transceiver 414 may employ the firstTX path 416 to transmit data when the end device 410 is connected toexternal power. As illustrated, the first TX path 416 may include a 1 Wpower amplifier that can dynamically adjust transmission power to 1 W,which can be enabled and/or disabled by the microcontroller 412. In someexamples, the transceiver may employ the second TX path 418 to transmitdata when the end device 410 is powered by internal power. In someexamples, the RF transceiver 414 may employ the RX path 420 to receivedata using antennas. In some examples, the microcontroller 412 maycontrol a single-pole double-throw switch 421 to select between thefirst TX path 416 and the second TX path 418 based on whether the enddevice 410 is connected to external power or internal power. In someexamples, the microcontroller 412 may control a single-pole double-throwswitch 422 to select between one of the TX paths 416 and 418, or the RXpath 420, based on whether the RF transceiver 414 is transmitting orreceiving data. In various embodiments, the first TX path 416, second TXpath 418, and/or the RX path 420 may include one or more SAW (surfaceacoustic wave) band pass filters or low pass filters that can limit abandwidth of the receiver, which in some embodiments can improve thermal(kTB) noise and can prevent out-of-band interference and attenuate thetransmission of harmonics at the transceiver 414.

In various examples, the end device 410 may include an internal antenna424 located inside of a housing of the end device 410 to transmit andreceive signals for the RF transceiver 414 over networks 210. In someexamples, the end device 410 may further include an external antenna 426located exterior to the housing of the end device to transmit andreceive signals for the RF transceiver over networks 210. In someexamples, the end device 410 may include one or more ports adapted tocouple the end device 410 with one or more external antennas. Themicrocontroller may control whether the RF transceiver 414 uses theinternal antenna 424 or the external antenna 426 using a single-poledouble-throw switch 428. For instance, if the end device 410 is in anenvironment where RF signals have trouble reaching (e.g., metal box,basement of a building, etc.), if a received signal strength is below athreshold, or if a transmission has not been received or acknowledged,the microcontroller 412 may be programmed to select the external antenna426, which may be positioned outside of the environment.

In various embodiments, the end device 410 may be powered through anexternal power supply, such as USB (universal serial bus) power 429,which may provide power at various voltages, such as 5 volts. In otherexamples, wall connection may power the end device 410. In someexamples, the end device 410 may include a USB-to-UART converter 430which receives power through the USB power 429. In some examples, theUSB 429 further comprises a USB bridge that can be used for variouscommunications, such as diagnostics and/or firmware or software updatesto the end device 410.

In some examples, the end device 410 includes one or more batteries 432and one or more supercapacitors 433 which serve as an internal powersupply. In some examples, the batteries 432 and supercapacitors 433 maypower components of the end device 410 (e.g., microcontroller 412, RFtransceiver 414, etc.). In some examples, the end device 410 may includea gas gauge 434. The gas gauge 434 may include a coulomb counter with anintegrated buck-boost converter. In some examples, the gas gauge 434 maylimit current that flows from the batteries 432 to charge thesupercapacitor 433. Further description of the batteries 432 and thesupercapacitor 433 can be found in the description for FIG. 6B.

In some examples, the end device 410 may include a diode 435, such as anOR diode, that may be controllable by the microcontroller 412, or mayautomatically select between external power (e.g., the USB power 429) orinternal power (e.g., the batteries 432 and the supercapacitor 433). Insome instances, the end device 410 includes various switching supplies436, such as a 2.1V buck converter, a 2.048 V VREF, and/or a 5V boostconverter. In some examples, the switching supplies 436 may step up, orstep down, the voltage of the power supplied the external power supplyor the internal power supply based on the voltage ratings for poweringcomponents in the end device 410.

In some examples, the end device 410 may include one or more sensors 438for measuring conditions inside of the end device 410 and/or in theenvironment of the end device 410. In some examples, the sensors 438 mayinclude a relative humidity sensor, a pressure sensor, and/or atemperature sensor. The microcontroller 412 may control the sensors 438and/or receive measurements from the sensors.

In some instances, the end device 410 may include a plug-of-nailsinterface 440 to receive a plug-of-nails connector. In some instances,the plug-of-nails interface 440 may receive a connection of aplug-of-nails cable to program the microcontroller 412 and/or processorsincluded in the microcontroller 412. In some instances, theplug-of-nails interface 440 may comprise a contact with one or morethrough-holes and connection points for a plug-of-nails connector toenter and contact. In this way, the plug-of-nails interface 440 may savespace on the circuit board, lower bill of material (BOM) cost, and lowerinventory load of the end device 410 because no mechanical piece ofequipment is populated on the board.

In some examples, the end device 410 may include one or more lightemitting diodes (LEDs) 442. The LEDs 442 may include four MCU LEDs thatare not externally visible, one power LED (e.g., such as an LED 1219,described below in connection with FIG. 12) that is on when externalpower is supplied, and two LEDs (one LED for USB transmit and one LEDfor USB receive) that are not externally visible for the end device 410when inside an enclosure 1100, described below in connection with FIG.11.

In some examples, the microcontroller 412 includes a sensor interface444 for communicating with various sensors, such as sensors 114, 116,and/or 302. In some examples, the sensor interface 444 may include oneor more hardware ports configured to communicatively couple the enddevice 410 with the sensors, such as through one or more cables. In someinstances, the sensor interface further includes one or more components,modules, and/or circuits to receive data and store the data from thesensors. In some examples, the sensor interface 444 is configured tocouple with multiple sensors, including but not limited to 3-wireAutomatic Meter Reading (AMR) sensors, Hall effect sensors, reed switchsensors, pulses sensors, and magneto-resistive sensors. In someinstances, the sensor interface 444 may include any wired or wirelessinterface. Further description of the sensor interface 444 can be foundin the description of FIG. 6B.

In some embodiments, the sensor interface 444 can be coupled to aninterrupt at the microcontroller 412 which can increment the totalizer.In some embodiments, the totalizers can be implemented as hardware,software, or firmware in the microcontroller 412. In some embodiments,the totalizer can be resettable from the gateway device 306. In someembodiments, a time of the last observed pulse (or all observed pulses)can be kept in memory at the microcontroller 412, and can be transmittedto the gateway device 306 with the meter count. In some embodiments, theinterface 444 includes edge-triggered port interrupts.

In some embodiments, the microcontroller 412 includes an ASCII readerconfigured in accordance with a SENSUS protocol. In some embodiments,this can provide another implementation for a sensor to communicate withthe end device 410. In some embodiments, communications can occur via a3-wire interface in accordance with the SENSUS protocol. In someembodiments, sensor data is read from the SENSUS register (e.g., asASCII characters) via the sensor interface 444. The time of each lastread can be kept in memory and communicated back to the gateway device306 with the meter count.

In some embodiments, the microcontroller 412 includes a send datafunction that can automatically send data at intervals, where the datainterval time can be programmable by the gateway device 306 or theservice provider 206. In one example, a reporting interval can be on theorder of every second, one or more minutes, hourly, daily, weekly,monthly, etc. In some embodiments, the end device 410 can transmitinformation when queried by the gateway device 306. Thus, the end device410 can operate both in a push mode or a pull mode to transmit data tothe gateway device 306.

In some embodiments, the microcontroller 412 can include dynamic controlof the RF transceiver. In some embodiments, this allows themicrocontroller 412 to optimize the radio link function to determine theoperating configuration of the transceiver 414 by analyzing the linkbetween the end device 410 and the gateway device 306. In someembodiments, optimization will balance radio operation with batterylife. For example, at least two general modes of radio link optimizationcan be selectable. In some embodiments, these radio link modes can beselected by the gateway device 306 and/or by the service provider 206,for example.

By way of example, a first mode may be provided to conserve thebatteries of the end device 410. For example, the LoRa (or any low powerwireless area network protocol) PHY link RF transmit power, bandwidth(BW), and spreading factor (SF) can be dynamically controlled insoftware to minimize power consumption and maximize range capabilitywithout the need to change hardware configuration. In some embodiments,this dynamic control can be based on a received-signal-strengthindicator (RSSI), signal-to-noise ratio (SNR), packet error rate (PER),and channel activity detection (CAD). For example, the gateway device306 can indicate to the end device 410 the lowest power required toprovide a signal to the gateway device 306.

In some embodiments, a second mode can be provided that configures theradio in the end device 410 for the strongest radio link (e.g., 1 watt)at the expense of using more battery power.

In some embodiments, the end device 410 can monitor the health of theend device 410. By monitoring specific parameters of the end device 410(such as battery power, supply voltage, memory status, memoryutilization, temperature, humidity, reporting frequency, data samplingrate, signal strength, location, etc.) the health of end device 410 canbe monitored and reported back to the gateway device 306, and then on tothe service provider 206, for example. In some embodiments, end devicehealth can be reported back to the gateway device only when there is achange in one or more parameters (or a change is above or below athreshold) in order to minimize data transfer, which in turn can extendbattery life.

In some embodiments, the end device 410 can include a real-time clock(RTC) in order to time stamp sensor data and to initiate time-drivenevents such as sleep periods, transmit events, and to coordinate receiveslots. In some embodiments, the real-time clock can be implemented inhardware, software, and/or firmware to keep track of time.

FIG. 5 shows a device 500 illustrating details of a transceiver, such asthe transceiver 404 of FIG. 4A and the RF transceiver 414 of FIG. 4B,for example. In some embodiments, the transceiver 500 is a LoRatransceiver, such as a SEMTECH transceiver. In some embodiments, thetransceiver 500 may implement any wireless communication protocol inaccordance with the SEMTECH transceiver.

In some embodiments, the transceiver 500 can include transmit/receive(TR) control of a SPDT (single pole, double throw) switch. In someembodiments, independent receive and transmit paths can allow forimpedance matching customized for each path. For example, impedancematching can provide approximately a 2 dB gain in the link budget. Insome embodiments, two or more antennae can be used in addition to orinstead of the SPDT switch.

In some embodiments, the SEMTECH module has two pins available fortransmit: RFO_HF (22), which has a transmission power of −4 dBm to +14dBm; and PA_BOOST: −2 dBm to +20 dBm. In some embodiments, the formerpin provides high efficiency, while the latter pin can be lessefficient, but can provide better transmission range. In someembodiments, the transmission pin can be selected dynamically inaccordance with one or more instructions received from the gatewaydevice 306, for example.

FIG. 6 illustrates an embodiment of a power supply 602 which can beimplemented in the end device 400 of FIG. 4A and/or the end device 410of FIG. 4B.

In some examples, the power supply 602 may include an external powersupply 604 and an internal power supply including internal batterysupply 606 and supercapacitor 608. In various examples, the power supply602 may include a power select 610 to select between the external powersupply 604 and the internal power supply including the internal batterysupply 606, with selected power output to supercapacitor 608. In variousexamples, one or more of the external power supply 604 or the internalpower supply including the internal battery supply 606 and thesupercapacitor 608 may provide power to one or more switching supplies612, which in turn provide power to various components of the end device400 and/or end device 410.

In some examples, the external power supply 604 may comprise powersupplied through a USB port of the end device 410 (e.g., USB 429). Insome examples, the supply voltage VUSB 614 may comprise a voltagesupplied through a USB port ranging from 4.0 volts to 5.25 volts. Theexternal power supply 604 may further include a 3.8-volt buck converter616 configured to receive a voltage between 4 volts to 40 volts and stepthe voltage down to 3.8 volts to supply power to the end device 410.While illustrated as being a USB power source, the external power supply604 may additionally or alternatively comprise any type of externalpower supply, such as wall power.

The power supply 602 may further include an internal power supplycomprising the internal battery supply 606 and supercapacitor 608. Insome examples, the internal battery supply 606 may include a batterybank 618, a battery switch 620, and an auxiliary battery connector 622.In some instances, the battery bank 618 may include one or morebatteries arranged in series or parallel to provide power to the enddevice 410. In some instances, the battery bank 618 may include any typeof battery, such as lithium thionyl chloride (Li—SOCl₂), and compriseany number or size of batteries. The battery switch 620 may be any typeof switch (e.g., single-pole single-throw) controlled by amicrocontroller, such as microcontrollers 402 and/or 412, configured toselectively allow the battery bank 618 to provide power to thecomponents and circuitry of the end device 410. For example, the batteryswitch 620 may be a physical toggle switch operable to isolate theinternal battery supply 606 from the power supply 602 to prevent thebattery bank 618 from draining during transport. The auxiliary batteryconnector 622 may comprise any type of hardware connector withelectrical connections to connect to the battery bank 618 and provideelectrical paths from the battery bank 618 to the circuitry of the powersupply 602. In some examples, the internal battery supply 606 may chargethe supercapacitor 608.

The supercapacitor 608 may comprise a supercapacitor balancer circuit624, a first capacitor 626, and a second capacitor 628. In someinstances, the first capacitor 626 comprises a single capacitor, or twoor more capacitors in series. In some instances, a number of capacitorsmay be selected based on an amount of energy to store, voltagerequirements, transmission power, etc. In some instances, the secondcapacitor 628 may comprise any number of capacitors, similar to thefirst capacitor 626. In some examples, the supercapacitor balancercircuit 624 may include various components, including resistors,capacitors, and operational amplifiers. However, other types ofsupercapacitor balancing circuits may be implemented as thesupercapacitor balancer circuit 624. In some examples, thesupercapacitor balancer circuit 624 may operate to prevent anover-voltage problem and/or an over-current problem occurring with thecapacitors 626 and 628. For example, the supercapacitor balancer circuit624 may prevent the capacitors 626 and 628 from damage caused by toomuch voltage or current supplied from the internal battery supply 606.In various examples, components of the supercapacitor balancer circuit624 may include one or more 10 mega ohm resistors, as illustrated. Theselection of these relatively high value resistors may result inbenefits, such as less current loss. For example, the supercapacitorbalancer circuit 624 may have an input voltage of 3.6 volts up to 4.2volts. While simple passive resistors may work in place of the activesupercapacitor balancer circuit 624, resistors around the range of 1mega ohm may result in wasted current due to losses, such as 4 microamps of wasted current. In some examples, this may be a significantamount of loss (e.g., 15% of total consumption). Accordingly, theselection of the 10 mega ohm, or another similarly high resistance, mayresult in less wasted current, which may lengthen the life of thebattery bank 618.

In some examples, the first capacitor 626 and the second capacitor 628may be placed in parallel and receive power through the supercapacitorbalancer circuit 624. In some examples, the first capacitor 626 and thesecond capacitor 628 may comprise roughly 0.5 farad capacitors (e.g.,0.47 F) that, when placed in parallel, result in a 1 farad capacitance.The supercapacitor balancer circuit 624 may charge the first capacitor626 and the second capacitor 628 using power supplied from the internalbattery supply 606.

In some examples, the power supply 602 may include a gas gauge 630, suchas gas gauge 434 of FIG. 4B. In some examples, the gas gauge 630 mayinclude a 3.6-volt buck-boost converter to adjust the voltage from thebattery bank 618 to be approximately 3.6 volts. In some examples, thegas gauge 630 may further include a coulomb counter. The coulomb countermay count the coulombs (e.g., amp-seconds) leaving the battery bank 618to charge the supercapacitor 608 during the low power mode to determinetotal energy out of battery bank 618 and/or how much energy remains inthe battery bank 618. In some examples, the gas gauge 630 may limit theamount of current leaving the battery bank 618 from surpassing athreshold current to prevent the battery bank 618 from discharging tooquickly when charging the supercapacitor 608. In some examples, this mayextend the life of the battery bank 618.

In some examples, the power select 610 may select between the externalpower supply 604 and the internal battery supply 606. In some examples,the power select 610 may comprise one or more switches, transistors, orother components controlled by a microcontroller (e.g., microcontroller412) to select between the external power supply 604 and the internalbattery supply 606. In some examples, the power select 610 may selectthe external power supply 604 to function as the source for power supply602 when the end device 410 is connected to external power, andotherwise select the internal battery supply 606.

In some examples, the switching supplies 612 may receive power, eitherfrom the external power supply 604, or the internal power supplyincluding the internal battery supply 606 and the supercapacitor 608.The switching supplies 612 may regulate the voltage received from thepower sources (internal or external) and switch the voltage toappropriate voltages for various components of the end device 410. Theswitching supplies 612 may include a 2.048 volt ADC reference, a 3.3volt LDO voltage regulator for a single pole double throw switch fortransmission, such as single-pole double-throw switch 421, a 2.1 voltbuck converter for various system components (e.g., microcontroller 412,RF transceiver 414, diodes, op-amps, etc.), and a 5 volt boost converterfor a sensor interface (e.g., sensor interface 444).

In examples where the internal battery supply 606 is selected by thepower select 610 to serve as the power supply 602, the supercapacitor608 may be discharged, and then recharged by the internal battery supply606. In some examples, the supercapacitor 608 may be charged anddischarged according to a duty cycle, where the duty cycle is controlledby one or more of the microcontroller 412 and/or RF transceiver 414.

In some examples, the end device 410 may only transmit resourcemeasurement data collected by sensors at various intervals. When the enddevice 410 is not transmitting data, the RF transceiver 414 andassociated circuitry may be powered down in a low power mode. In thisway, when the end device 410 is not transmitting, power may be saved toextend the life of the battery bank 618. In some examples, the dutycycle may have a longer time period for the lower power mode when datais being stored (e.g., 30 seconds, 1 minute, 5 minutes, etc.), than acommunication mode when data is being transmitted (e.g., 10milliseconds, 100 milliseconds, etc.). In some examples, themicrocontroller 412 may employ the RF transceiver 414 to transmitrelatively high power signals (e.g., ½-watt, 1-watt, etc.). In suchexamples, the power provided by the internal battery supply 606 may beinsufficient, and the supercapacitor 608 may be used to power thecircuitry of the RF transceiver 414. For example, the supercapacitor 608may provide the 1 W power amplifier and the RF transceiver 414 with upto 1.5 W of power, enabling the RF transceiver 414 to transmit the highpower signals. In some examples, the supercapacitor 608 may at leastpartially discharge when providing power to the RF transceiver 414 inthe communication mode. Once the supercapacitor 608 has finishedsupplying power to the RF transceiver 414 to transmit a signal, thebattery bank 618 may recharge the supercapacitor 608 during the lowpower mode for the longer periods of time to charge the supercapacitor608 for the next transmission. In this way, the end device 410 mayreceive and store resource measurement data from sensors using theinternal battery supply 606 while in the low power mode, and transmitresource consumption data periodically using relatively high powersignals powered by the supercapacitor 608. In some examples, thecommunication mode and low power mode intervals may be set or based onthe transmission power of the signals.

In some examples, the intervals for the communication mode and low powermode may be dynamically adjusted or determined based on the remainingcharge in the battery bank 618. For example, the coulomb counter maydetermine that the battery bank 618 is running low, and lengthen theinterval of the low power mode.

In some examples, the internal battery supply and/or supercapacitor 608may further act as an uninterrupted power supply (UPS) for the enddevice 410 when an external power supply 604 is connected, but isproviding interrupted power.

In various examples, the power supply 602 or a portion of the powersupply 602 (e.g., internal battery supply 606, battery bank 618,supercapacitor 608, etc.) may be thermally coupled to a heat sink. Forexample, the end device 410 may include a heat sink which may be coupledto an external heat sink, depending on an installation. In someexamples, the internal components of the end device 410 may be coupledto a heat sink, such as a pipe, that maintains a relatively stabletemperature and may serve as a heat sink. Further, heat sink may beintegrated into an installation bracket, which may be clamped to a pipeusing one or more hose claims, thereby improving operation of the enddevice 410 and ease of installation.

FIG. 7 illustrates an example process 700 for transmitting a signal, bya transceiver of an end device (e.g., computing device), according to aduty cycle of the end device. The operations of the process 700 may beperformed by one or more of software, hardware, firmware, or acombination thereof, of the end device.

At 702, the process 700 may cause the end device (e.g., end device 400,end device 410, etc.) to enter a low-power mode for a first predefinedperiod of time. In some examples, the end device may limit or removepower from various portions of the end device during the low-power mode(e.g., RF transceiver 414, components 420, 422, 428, etc.). In someexamples, the end device may still power other portions of the device,such as portions which receive and store data from one or more sensors(e.g., microcontroller 412, sensor interface 444, etc.). For example, ina case where a 3-wire AMR sensor is coupled to the end device 410, theentire end device 410 (aside from a timer mechanism) shuts down inbetween meter reads (e.g., for 5 to 60 seconds). In some instances, wheninterfacing with a reed switch, magneto-resistive sensor, or Hall effectsensors, the micro control unit on the end device 410 may wake upfrequently to sample the sensor (e.g., to wake up for 50 μs every 5 ms,or about 1% duty cycle.)

At 704, the process 700 may cause the end device to switch from thelow-power mode to a communication mode for a second period of time. Insome examples, the end device may switch to the communication mode basedat least in part on detecting an end of the first predefined period oftime. In some examples, the second period of time may be less (e.g., 10milliseconds, 100 milliseconds, etc.) than the first predefined periodof time (e.g., 30 seconds, 1 minute, 5 minutes, 15 minutes, etc.). Invarious examples, the end device may consume less power while in thelow-power mode than the communication mode. In some examples, switchingto the communication mode may comprise turning on or providing power tovarious components of the end device (e.g., RF transceiver 414,components 420, 422, 428, etc.).

At 706, the process 700 may cause an RF transceiver (e.g., RFtransceiver 414) to transmit a signal representing a portion ofmetrology data collected by one or more water sensors to a gatewaydevice. In some examples, a supercapacitor (e.g., supercapacitor 608)may power the RF transceiver and other components required to transmitthe signal. In some examples, the signal may comprise a high powersignal (e.g., ½-watt, 1-watt, etc.). As may be understood, althoughdescribed in connection with water data, aspects of this disclosure maybe applied to one or more sensors configured to monitor data associatedwith any resource.

At 708, the process 700 may cause the end device to enter the low-powermode for the first predefined period of time. In some examples, thecomputing device may enter the low-power mode in response to completingthe transmitting of the signal. In some examples, the computing devicemay enter the low-power mode in response to detecting an end of thesecond period of time. In some examples, the computing device may enterthe low-power mode in response to receiving an ACK from the gateway,indicating that a transmission from the end device to the gateway hasbeen received.

Thus, the process 700 illustrates an example of a duty cycle for an enddevice, where the transmission that occurs in the communication mode ispowered by a supercapacitor to transmit a higher power signal

FIG. 8 illustrates an example sensor interface 802 (e.g., sensorinterface 444) which enables an end device, such as end device 400and/or end device 410, to communicate with various sensors, such assensors 114, 116, and/or 302. The sensor interface 802 includes a sensorconnection 804, which includes three input ports, where each input portreceives a wire, cable, input jack, or any other connector. As shown,port 1 and port 2 each have electrostatic discharge (ESD) protection 806in the form of Zener diodes connected to ground. However, in otherexamples, the ESD protection 806 may comprise another type of ESD orother transient voltage protection. Port 3 provides a ground input portfor various sensors that are connected to the sensor connection 804.

Port 1 is electrically connected to an AMR power clock generator 808,and port 2 is electrically connected to a pull-up resistor 810 and apull-up resistor enable 812. Port 2 further maps to a data comparator814 and a comparator power switch 816.

In some examples, port 2 comprises a data port which receives data fromthe sensors connected to the sensor connection 804. Depending on thetype of sensor, only port 2 need be utilized to collect data. Forexample, a reed switch sensor is connected, only one cable plugged intoor connected to port 2, and grounded through port 3, is required tocommunicate data via the sensors interface 802.

In examples where a Hall effect sensor, a magneto-resistive sensor, or areed switch sensor is connected, the pull-up resistor enable 812 may beactivated to “pull up” the pull-up resistor 810 by placing a voltage atport 2 that corresponds to a voltage for communicating with a Halleffect sensor, a magneto-resistive sensor, a reed switch sensor, or anyother sensor with an open drain or open collector output. For example,the microcontroller 412 may employ a P-channel MOSFET of the pull-upresistor enable 812 to turn on the pull-up resistor on or off dependingon whether the sensor output is open collector/open drain or push-pull,respectively.

In examples where the microcontroller 412 turns on the P-channel MOSFETto cause the pull-up resistor enable 812 to turn on the pull-up resistor810 to accept input from a Hall effect sensor, a magneto-resistivesensor, or a reed switch sensor via port 2 of the sensor connection 804,the data comparator 814 and comparator power switch 816 receive the datainput from the sensor. In some examples, one or more modules, which maycomprise software, may cause the microcontroller 412 to configure thedata comparator 814 and comparator power switch 816 to count powerpulses from the sensors.

In some examples, the sensor input into the sensor connection 804 maycomprise one of an AMR sensor or a pulse sensor. In such examples, theAMR sensor or pulse sensor may plug into all three ports of the sensorconnection 804. The AMR power and clock generator 808 circuit mayprovide power and timing to the AMR sensor or pulse sensor throughport 1. However, in examples where the sensor comprises an AMR sensor orpulse sensor, the microcontroller 412 will only cause the pull-upresistor enable 812 to turn on the pull-up resistor 810 when the sensoroutput is an open collector/open drain, otherwise, pull-up resistorenable 812 turns off pull-up resistor 810 for sensors with push-pulloutputs. Similar to the other types of sensors, the comparator powerswitch 816 may be selectively turned on and off according tosoftware-based duty cycle by the microcontroller 412 to receive pulsesfrom a sensor using the data comparator 814. In some examples, the datacomparator 814 may store the sensor pulse data in a register of the enddevice 410.

Regardless of the type of sensor, software-based modules cause themicrocontroller 412 to selectively activate the comparator power switch816 (e.g., by activating the P-channel MOSFET), which in turnselectively powers the data comparator 814 to turn on and collect pulsedata from the sensors, and turn back off after collecting the dataaccording to the duty cycle. In some examples, by pulsing the datacomparator 814, the duty cycle may minimize power consumption forcounting power pulses from the sensors.

In some examples, the duty cycle may depend on the type of sensor. Forexample, various sensors may have different rotational speeds and/ordifferent sensor outputs, and the duty cycle may be adjusted to ensurethat the data comparator 814 is turned on to receive and store the data,but turned off when the sensors are not providing data via port 2 of thesensor connection 804. Further description of these techniques are foundbelow with reference to the processes of FIGS. 9 and 10.

FIG. 9 illustrates an example process 900 for determining a sensor typeof a sensor associated with an input cable coupled to a first inputport, and applying a voltage to an input port to receive data from thesensor based on the type of sensor. In some examples, themicrocontroller 412 of end device 410 may perform the techniques ofprocess 900.

At 902, the process 900 may determine a sensor type of a sensorassociated with an input cable coupled to the first input port. In someexamples, the input port may correspond to port 2 of the sensorconnection 804. In various examples, the sensor type is a first sensortype, and the sensor comprises at least one of a reed switch sensor, aHall effect sensor, or a magneto-resistive sensor. In other examples,the sensor type is a second sensor type, and the sensor comprises atleast one of a pulse sensor or an AMR sensor.

In some examples, determining the sensor type may comprise receiving,through a USB cable plugged into a USB port of the end device 410, anindication of the sensor type. For example, a computing device (e.g.,computing device 208) may connect to the end device 410 to provide theindication of the sensor type. In some examples, determining the sensortype may comprise receiving, via the RF transceiver 414 and from one ormore server computing devices (e.g., service provider(s) 206), a signalcomprising the indication of the sensor type.

At 904, the process 900 may, based at least in part on determining thesensor type, selectively provide a first voltage to the first input portor a second voltage to a second input port. In some examples, the firstvoltage is associated with a reed switch sensor, a Hall effect sensor,or a magneto-resistive sensor, and the first port comprises port 2 ofthe sensor connection 804. In some examples, the second voltage isassociated with a pulse sensor or an AMR sensor, and the second portcomprises port 1 of the sensor connection 804.

In examples where the sensor type comprises a first sensor typeassociated with a reed switch sensor, a Hall effect sensor, or amagneto-resistive sensor, the microcontroller 412 may cause the pull-upresistor enable 812 to turn on the pull-up resistor 810. In exampleswhere the sensor type comprises a second sensor type associated with oneof a pulse sensor or an AMR sensor, the microcontroller 412 may causethe AMR power and clock generator 808 to turn on and place a voltageacross port 1 of the sensor connection 804, which may in turn power andprovide timing for the pulse sensor or the AMR sensor.

At 906, the process 900 may receive, by the comparator circuit,metrology data (e.g., resource consumption data) from the sensor. Insome examples, the microcontroller 412 may cause the comparator powerswitch 816 to activate the data comparator 814 to receive the dataaccording to a duty cycle.

At 908, the process 900 may store, by the comparator circuit, metrologydata from the sensor. In some examples, the microcontroller 412 maycause the comparator power switch 816 to activate the data comparator814 to store the data according to the duty cycle.

FIG. 10 illustrates an example process 1000 for receiving data by acomparator circuit (e.g., data comparator 814 and/or comparator powerswitch 816) according to a duty cycle. In some examples, the process1000 may be performed by software modules that control themicrocontroller 412.

At 1002, the process 1000 may cause a comparator circuit, a pull-upresistor circuit, and an AMR circuit to enter a low power mode for afirst period of time. In some examples, this may comprise themicrocontroller 412 turning off the AMR power and clock generator 808,the comparator power switch 816, and/or the pull-up resistor enable 812.

At 1004, in response to detecting an end of the first period of time,the process 1000 may cause the comparator circuit and at least one ofthe pull-up resistor circuit or the AMR circuit to switch from the lowpower mode to an active mode for a second period of time.

At 1006, the process 1000 may cause the comparator circuit to receiveand store pulses from a water sensor for a second period of time, thesecond period of time being less than the first period of time. In someexamples, the water sensor comprises a first type of sensor, and whereinthe first type of sensor comprises at least one of a reed switch sensor,a Hall effect sensor, or a magneto-resistive sensor. In other examples,the water sensor comprises a second type of sensor, and wherein thesecond type of sensor comprises at least one of a pulse sensor or an AMRsensor.

At 1008, in response to detecting an end of the second period of time,the process 1000 may cause the comparator circuit and the at least oneof the pull-up resistor circuit or the AMR circuit to switch from theactive mode to the low power mode for the first period of time.

In some examples, the process 1000 may further include determining arotational speed of the water sensor plugged into the one or more inputports, calculating the first period of time based at least in part onthe rotational speed, and calculating the second period of time based atleast in part on a rate at which the water sensor outputs pulses.

In various examples, the process 1000 further comprises receiving, fromone or more server computing devices, an indication of the first periodof time and an indication of the second period of time.

In some examples, the process 1000 may further include sendinghistorical rotational speed data associated with the water sensor to oneor more server computing devices, and receiving, from the one or moreserver computing devices, an indication of a third period of time, andadjusting the first period of time based at least in part on the thirdperiod of time.

FIG. 11 depicts an example housing 1100 for an end device, such as enddevice 410. In some examples, the housing 1100 may generally be aclamshell shaped enclosure having a top cap 1102 and a bottom cap 1104.One or more fasteners 1106 may fasten the top cap 1102 and the bottomcap 1104 together. In some examples, a gasket 1108 may be insertedaround a tongue-and-groove interior perimeter of the top cap 1102 andthe bottom cap 1104, such that, when the top cap 1102 and bottom cap1104 are fitted together in combination with gasket 1108, a water tightseal is created for the housing 1100 for the end device. In this way,gasket 1108 may minimize leak points inside of housing 1100. In someinstances, a PCB 1110 on which the components of the end device 410 areplaced may include openings 1112 through which the fasteners 1106 maypass through. As illustrated the housing 1100 may include connections1114 to provide an electrical connection for one or more sensors, asdiscussed herein.

In some examples, the fasteners 1106 are thermally coupled to the PCB1110 and serve as heat sinks for the housing 1100. Further, the examplehousing 1100 may include an external mounting bracket for mounting thedevice. In an implementation where the end device is a water metermonitoring water consumption for a water resource, the housing 1100 maybe installed via a bracket on a pipe using one or more pipe clampsaround the pipe and through the bracket. Further, the bracket and thepipe claims may be thermally coupled to the fasteners 1106 (and to thePCB, accordingly) to facilitate heat transfer from the end device to thepipe, for example.

In portions of FIGS. 4A-10, various components, and values for thosecomponents, are illustrated as being specific values. It is contemplatedthat, while the components and values depicted may be contemplated forsome embodiments of the claimed invention, in some examples, othercomponents or values may be selected that perform the same functions oroperations described herein. Unless otherwise stated, components may beadded, removed, or swapped, and other values may be utilized, forperforming the functions described herein.

Example Concentrator

FIG. 12 illustrates a graphic representation of an example concentrator1200, such as concentrator 262. In various examples, the concentrator1200 may comprise a single chip disposed on a single PCB and included ina gateway device, such as gateway device(s) 202. In some examples, theconcentrator 1200 may comprise a LoRaWAN® concentrator with antennadiversity, or simultaneous dual-band operation, including twoindependent RF paths, each with transmit and receive capability. Invarious examples, the concentrator 1200 may comply with variousinterface standards such as the XBee® interface standard. As discussedin the figures below, the concentrator 1200 may be of a relatively smallsize (e.g., 0.24 in³) and lightweight (e.g., 7 grams).

In various examples, the concentrator 1200 may generally be categorizedinto three portions: a CPU/power/interface portion 1202, a basebandportion 1204, and a radio portion 1206.

In some examples, the CPU/power/interface portion 1202 may include a32-bit RISC processor 1208 (e.g., ARM Cortex-M Processor) which controlsoperations of the concentrator 1200, such as power operations (e.g.,power supply control, switching supply 1220 control, etc.) and variousinterfacing operations (e.g., User LEDs 1210 interfacing, 16 MHzOscillator 1214 interfacing, 32.768 kHz RTC Ref 1216 interfacing, etc.).In various examples, the 32-Bit RISC processor 1208 may controloperations of the concentrator 1200 and can include hardware, software,or firmware to perform or support the following functions, including butnot limited to: 168 MHz CPU frequency; 1 MB flash; 192 KB of SRAM; up to18 general purpose externally-available input/output (GPIO); a GPIOspeed with maximum input/output toggling of 84 MHz; a crypto graphicalhardware accelerator for AES 128, 192, 256, Triple DES, HASH (MDS,SHA-1), and HMAC; timers including twelve 16-bit and two 32-bit; threeindependent 12-bit analog-to-digital (ADC) converters with a samplingrate of 2.4 MSPS and 5 externally available channels; oneexternally-available 12-bit digital-to-analog converter (DAC) with anupdate rate of 1 MSPS and one externally available channel; a real-timeclock (RTC) with an RTC reference of 32.768 kHz; one USB 2.0 port; twoUART ports; one serial peripheral interface bus (SPI); oneinter-integrated circuit (I²C); and/or an integrated temperature sensor.

The 32-bit RISC processor 1208 may receive user input to control four(or any number of) user-configurable LEDs 1210, and store data via SPIbus in 16 Mbit of flash memory 1212 external to the processor chip 1208,such as user data. The concentrator further includes a 16 MHz oscillator1214 to control the clock rate of the 32-bit RISC processor 1208, and a32.768 kHz real-time clock (RTC) reference 1216.

CPU/power/interface portion 1202 of the concentrator 1200 may furtherinclude a 20-pin XBee® header 1218. In this way, the concentrator 1200conforms with the industry standard form factor for XBee®. The 20-pinXBee® header 1218 may generally comprise a form factor compatible radiomodule that provides an input voltage of 2.7 volts to 5.5 volts to theswitching supplies 1220. In some examples, the switching supplies 1220may include a buck-boost converter to provide an output voltage of 3.3volts (0.8 amps), another buck-boost converter to provide an outputvoltage of 5 volts (1 amp), a buck converter to provide an outputvoltage of 1.8 volts (1.25 amps), and four low-noise low-drop out (LDO)regulators for powering sensitive loads of the concentrator 1200.Further, the XBee® headers 1218 may provide power to a power LED 1219 toindicate that the concentrator 1200 is powered on.

In some examples, the baseband portion 1204 of the concentrator 1200includes a baseband processor 1222 configured to manage functions of theconcentrator 1200 generally related to radio functionality. In someexamples, the baseband processor is designed for low-power, long rangecommunication technologies (e.g., LoRaWAN®, or other communicationprotocols). In some examples, the baseband processor 1222 may have areceive sensitivity of up to −142.5 dBm. In various examples, a 133 MHzoscillator 1224 may determine the clock rate of the baseband processor1222. In some examples, the baseband processor 1222 may control 5 LEDs1226 which indicate a status of both baseband 1204 and radio 1206. Insome examples, the 32-Bit RISC Processor 1208 may be programmable by auser of the concentrator 1200. For instance, the 32-Bit RISC Processor1208 may receive one or more Attention (AT) commands through aninterface, such as one of the USB interface or a UART interfaces. The ATcommands may comprise ASCII characters that the 32-Bit RISC Processor1208 is configured to process and understand. The AT commands mayprogram the 32-Bit RISC Processor 1208, and thereby the basebandprocessor 1222, to perform various functions, such as changing theoutput power to 1-watt or ½ a watt, or issuing control commands to theconcentrator 1200.

In various examples, the baseband processor 1222 may control two radiosof the concentrator 1200, such as radio 1228 and radio 1230, forcommunicating using two respective antennas, such as antenna 1232 andantenna 1234, for communicating over the network(s) 210. As illustratedin FIG. 12, radio 1228 and radio 1230 may include the same or similarcomponents to perform the same or similar functions. Accordingly, radio1228 will be described, and the components of radio 1230 may performsimilar functionality using similar components.

Radio 1228 may include a front-end transceiver 1236 configured toprocess a signal at a particular frequency or frequency range. In someexamples, the front-end transceiver 1236 may include components toprocess a modulated signal received through the antenna 1232 intosignals suitable for input into the baseband processor 1222, oralternatively module data received from the baseband processor 1222 intosignals suitable for transmission using the antenna 1232. In someexamples, the radio 1228 may include a transmit path including balun1238, a 1-watt power amplifier 1240, and a low pass filter 1242. Invarious examples, the balun 1238 may convert between two receivedsignals, such as a transmit differential pair (e.g., a balanced pair)received from the front-end transceiver 1236. The balun 1238 may outputan unbalanced signal to the 1-watt power amplifier 1240, which amplifiesthe balanced signal up to a signal power of 1-watt for transmission. Asigned of up to 1-watt in power may pass through the low pass filter1242 to attenuate frequencies higher than the cutoff frequency of thelow pass filter 1242, especially harmonic frequencies, to ensureelectromagnetic compliance (EMC) with regulatory agencies such as theFCC. In some examples, the radio 1228 may further include a single-poledouble-throw switch (SPDT) 1244 that is controlled by the basebandprocessor 1222 to select between the transmission path and a receivepath of the radio 1228. The 1-watt unbalanced, filtered signal may passthrough a lumped element low pass filter 1246, and in turn, may becommunicated over the network(s) 210 via the antenna 1232.

As noted above, the radio 1228 may further include a receive path forreceiving signals via the antenna 1232. The received signals maysimilarly pass through the lumped element low-pass filter 1246 and theSPDT switch 1244. The received signals may pass through the receive pathto reach the front-end transceiver 1236, where the receive path mayinclude a first surface acoustic wave (SAW) filter 1248, a low-noiseamplifier (LNA) 1250, and a second SAW filter 1252. In some examples,the SAW filter 1248 and SAW filter 1252 may comprise bandpass filters.In various examples, the first saw filter 1248 may limit the frequencyfrom the antennas to prevent the LNA 1250 from saturating, and thesecond SAW filter 1252 may help with out-of-band rejection of signals onthe received signal.

Thus, the concentrator has two radios, or radio 1228 and radio 1230, andtwo antennas 1232 and 1234 which allows for diversity. Each radio mayinclude a complete transmit and a complete receive path, and arecompletely redundant (e.g., channels on the same frequency may useeither antenna 1232 or antenna 1234 based on the stronger signal). Insome examples, the two radios and respective antennas allow forsimultaneous dual channels. For example, one channel may operate at onefrequency (e.g., 902 MHz), such as the low end of the medical radio(ISM) band, and one channel that operates at a second frequency (e.g.,928 MHz), such as a high end of the ISM band. As another example, foroperation in European ISM bands, one channel may operate at onefrequency (868 MHz) in order to receive LoRaWAN data, and one channelthat operates at a second frequency (433 MHz) to allow for directreceipt of Wireless M-Bus. Additionally, each radio 1228 and 1230 isconfigured to transmit signals at a high signal power, such as 1-watt.Thus, the concentrator 1200 can communicate low-bandwidth signals overlong distances using the high power signals.

In some examples, the 32-bit RISC processor 1208 may control theswitching supplies 1220 to supply the 1-watt power amplifiers 1240 and1258 of the radios 1228 and 1230 with various voltages depending on thetransmit power. For example, the switching supplies 1220 may provide the1-watt power amplifiers 1240 and 1258 with 5 volts for 1-watt signaltransmissions, or provide the 1-watt amplifiers 1240 and 1258 with 3.75volts for ½ watt signal transmission. In some examples, the differingvoltages may maintain a 65% efficiency for the 1-watt power amplifiers1240 and 1258 by ensuring the amplifiers operate in saturation. Invarious examples, the 32-bit RISC processor 1208 may turn on or offvarious power supplies, such as turning off the 5V buck-boost converter(or, more accurately, allowing the supply to enter power-efficientdiscontinuous modes) when the concentrator 1200 is not transmitting,which may conserve power.

In various examples, all the components discussed in FIG. 12 as beingincluded the concentrator 1200 may be positioned on a single chip (e.g.,the concentrator 1200). The components discussed may be selected basedon them having a small form factor. For example, the concentrator 1200may have a shield height under a 2-millimeter. The components of theconcentrator 1200 may be selected based on their form factor. Forexample, the lumped element low pass filters 1246 and 1264, and SAWfilters 1248, 1252, 1266, and 1270 may be selected for their small formfactors. Other components of the concentrator 1200 may similarly havesmall form factors to reduce the size of the concentrator 1200. In someexamples, the size of the concentrator 1200 may be 0.24 in³ and have aweight of 7 grams. For example, the concentrator 1200 may havedimensions of 1.3″×0.96″×0.19″ while still complying with the XBee®interface standard.

FIG. 13 illustrates a component layout of an example concentrator 1300,such as the concentrator 1200. The example component layout of theconcentrator 1300 depicts positions of the various LEDs on theconcentrator. For example, the four user-configurable LEDs 1210 arepositioned at the top of the component lay out and outside of theshields, so that they remain visible even when the radio shields are inplace. Further, the 5 LEDs 1226 which indicates the status of radio 1206and baseband 1204 are positioned at the bottom of the component lay out,outside of the perimeter of the shield so they remain visible after theshield is installed. Further, the one power LED 1219 is positioned nearthe 5 LEDs 1226. The example concentrator 1300 component layout alsodepicts the positions of TVS and ESD diodes, placed next to everyelectrical connection available external to the shields, which allowsfor the example concentrator 1300 to be installed outside of ESD-safeenvironments. For example, the example concentrator 1300 could beretrofitted in the field without concern for device damage due to humanhandling.

FIG. 14 illustrates example exterior views of a concentrator 1400, suchas concentrator 1200, which illustrate dimensions of the concentrator1400. As shown, the concentrator 1400 may have a length 1402 of 1.30inches, a width 1404 of 0.96 inches, and a height 1406 of 0.19 inches,not including the height of the pins. Including the height of the pins,the total height 1408 of the concentrator may be 0.33 inches.

FIG. 15 illustrates the small form factor of a concentrator 1500, suchas concentrator 1200, relative to a quarter 1502 to give reference as tothe small size of the concentrator 1500.

Example Graphical User Interfaces

Exemplary graphical user interfaces illustrating one or more alerts,signatures, reports, analysis, and/or historical data are shown in FIGS.16-23B. As can be understood in the context of this disclosure, theservice providers(s) 206 can analyze data received from the gatewaydevice(s) 202 and/or from the end device 204, and can generate alerts,signatures, reports, and or GUIs, and transmit the alerts, signatures,reports, and/or GUIs to the computing device(s) 208 (and/or to thegateway device(s) 202) for display as a GUI or as an audio alert.

FIG. 16 shows a graphical user interface (GUI) 1600 illustrating asuspected event report and/or alert. In some embodiments, the GUI 1600illustrates an email indicating a suspected operational waste alert. Insome embodiments, the alert/report identifies potential remedies andprovides instructions of how to identify the suspected operationalwaste. In some embodiments, the GUI 1600 may include images, pictures,and/or diagrams indicating where and/or what to look for to identify andcorrect the suspected event. In some embodiments, the images may reflectactual installation of equipment at a monitoring location, while in someembodiments, the image can reflect generic images based upon a modelnumber of a particular piece of equipment. Further, the GUI 1600 caninclude a graph indicating water usage and one or more annotationsindicating the suspected event, and/or the GUI 1600 can include a linkto the graph.

FIG. 17 shows a graphical user interfaces (GUI) 1700, illustrating waterusage for a monitoring location. In some embodiments, the GUI 1700illustrates a comparison of resource usage between two or more days. Insome embodiments, the GUI 1700 can be annotated to indicate suspectedmechanical or operational waste. In some embodiments, the GUI 1700illustrates instantaneous water usage as a number of gallons consumedevery minute. In some embodiments, the GUI 1700 illustrates an hourlyweather and temperature, as well as a cumulative total of water usagethroughout the day. In some embodiments, a user may toggle throughvarious days to compare a current water usage with any historical dataat a same and/or different location.

FIG. 18 shows a graphical user interface (GUI) 1800 illustrating waterusage for a monitoring location. In some embodiments, the GUI 1800illustrates analytics-generated annotations. In some embodiments, theannotations may be added manually, automatically, or may be flagged byan automated process and reviewed by a user. In some embodiments, theGUI 1800 can include visual representations of resource consumption bynodes or equipment at a monitoring location. As one non-limitingexample, if a monitoring location includes three nodes, a GUI canillustrate three individual instantaneous resource consumption graphsfor each node, with a further graph illustrating a total resourceconsumption. Further, node traces can be annotated or categorizedaccording to an individual node's deviation from a historical orexpected resource consumption value. In some embodiments, a user canselect within a total resource consumption graph, causing an additionaldisplay to illustrate individual node contributions to the totalresource consumption amounts. Thus, in this manner, a GUI can presentseveral layers and resolutions of data to a user to understand aresource consumption at a total and/or node level.

FIGS. 19A, 19B, 19C, and 19D show an automated waste event 1900 trackingsystem. For example, FIGS. 19A-D provide an interface for a user togenerate a report to one or more customers or email addresses to reportand provide one or more recommendations to mitigate the waste event. Forexample, the system allows a report to be generated includingrecommendation and/or images reflecting resource usage.

FIG. 20 shows an analytics log 2000 for detected waste events, such asfor a car wash location. In some embodiments, the analytics log 2000provides a high-level indication of waste events which can provide aninterface to link to more specific waste event reports, analytics, andrecommendations.

FIG. 21 shows an automated alert tracking page 2100. In someembodiments, the page 2100 provides a search capability, allowing a userto search by start date, end date, site, node purpose, status, events,classes of events, severity of events, etc. Further, the page 2100 canprovide links to more specific reports, statistics, and/orrecommendations for the various sites and resource usage data.

FIG. 22 shows a GUI 2200 for generating and managing alerts. Forexample, the GUI 2200 can generate text automatically for alertingsuspected waste events and for providing recommendations to remedy thesuspected waste.

FIGS. 23A and 23B show a GUI 2300 illustrating site information andanomalies. For example, FIG. 23A illustrates a left portion of analerting page, while FIG. 23B illustrates a right portion of thealerting page. In some embodiments, users may select one or more text,images, and/or links to receive specific information, reports,comparisons, and/or alerts regarding resource consumption information.

CONCLUSION

Although the present disclosure can use language that is specific tostructural features and/or methodological acts, the invention is notlimited to the specific features or acts described herein. Rather, thespecific features and acts are disclosed as illustrative forms ofimplementing the invention.

What is claimed is:
 1. A device comprising: a display; one or moreprocessors; and one or more non-transitory computer-readable storagemedia storing instructions that, when executed by the one or moreprocessors, cause the device to: receive resource consumptioninformation based on data collected at a resource consumption sensor;and present, on the display, a graphical user interface (GUI)comprising: a graphical representation of the resource consumptioninformation, the graphical representation comprising an x-axisrepresenting time and a y-axis representing an amount of resourceconsumption; and an interface element for toggling between displayingdata associated with a period of time comprising at least two of a day,a week, or a month.
 2. The device of claim 1, wherein the devicecomprises a first device and the resource consumption sensor comprises awater sensor coupled to a second device that communicates with the firstdevice.
 3. The device of claim 1, wherein the GUI further comprises atemperature indicator or a humidity indicator associated with theresource consumption information.
 4. The device of claim 1, wherein theinstructions, when executed by the one or more processors, further causethe device to receive a user input indicating whether a mechanicalfailure associated with a waste event is resolved.
 5. A devicecomprising: a display; one or more processors; and one or morenon-transitory computer-readable storage media storing instructionsthat, when executed by the one or more processors, cause the device to:receive resource consumption information based on data collected at aresource consumption sensor, the resource consumption informationincluding data associated with an occurrence of a waste event at amonitoring site location of a plurality of monitoring site locations;and present a graphical user interface (GUI) on the display, the GUIcomprising: a plurality of visual representations of the resourceconsumption information indicating a plurality of amounts of waterconsumption corresponding to the plurality of monitoring site locations;and an interface element for receiving a user input indicating whether amechanical failure associated with the waste event is resolved.
 6. Thedevice of claim 5, wherein the GUI further comprises one or moreidentifiers indicating one or more particular equipment at the pluralityof monitoring site locations.
 7. The device of claim 5, wherein the userinput comprises a first user input and the GUI further comprises aninterface link that, upon receiving a second user input, causes the GUIto present a report of a historical waste event associated with amonitoring site of the plurality of monitoring site locations.
 8. Thedevice of claim 5, wherein the user input comprises a first user inputand the GUI further comprises an interface link that, upon receiving asecond user input, causes the GUI to present a recommendation associatedwith a monitoring site of the plurality of monitoring site locations. 9.The device of claim 5, wherein the user input comprises a first userinput and the GUI further comprises an interface link that, uponreceiving a second user input, causes the GUI to present a resourceconsumption statistic associated with a monitoring site of the pluralityof monitoring site locations.
 10. The device of claim 5, wherein theinterface element comprises a first interface element and the GUIfurther comprises a second interface element to search the resourceconsumption information by at least one of a start date, an end date, amonitoring site, a node purpose, a status, an event, a class of event,or a severity of event.
 11. The device of claim 5, wherein the interfaceelement comprises a first interface element and the GUI furthercomprises a second interface element indicating that one or more of theplurality of monitoring site locations correspond to at least one of anirrigation equipment or a cooling tower equipment.
 12. The device ofclaim 5, wherein the interface element comprises a first interfaceelement and the GUI further comprises a second interface elementindicating an option to generate or send a report listing informationassociated with the resource consumption information.
 13. The device ofclaim 5, wherein the display comprises a smart phone display.
 14. Asystem comprising: one or more processors; and one or morecomputer-readable storage media storing instructions that, whenexecuted, cause the one or more processors to: determine resourceconsumption information based on data collected by a water sensor at aparticular monitoring site location; and cause a graphical userinterface (GUI) presented on a display to comprise one or more visualrepresentations of the resource consumption information indicating afirst node resource consumption amount, a second node resourceconsumption amount, and a total resource consumption amount based atleast in part on the first node resource consumption amount and thesecond node resource consumption amount.
 15. The system of claim 14,wherein the one or more visual representations comprise a number symbolrepresenting an amount of gallons of water consumed in units ofgallons-per-minute or gallons-per-day.
 16. The system of claim 14,wherein the system comprises a remote server device that provides ananalytics service to a mobile device.
 17. The system of claim 14,wherein the GUI further comprises an operational waste event trackingpage based on the resource consumption information.
 18. The system ofclaim 14, wherein the instructions, when executed, further cause thesystem to receive the resource consumption information from a watersensor associated with a commercial cooling tower.
 19. The device ofclaim 1, wherein the GUI further comprises an annotation indicating awaste event at a particular time on the x-axis.
 20. The device of claim5, wherein the interface element comprises a first interface element,the user input comprises a first user input, and the GUI furthercomprises a second interface element to, upon receiving a second userinput, provide additional details related to the waste event.